AW: AW: Dumb SQL question...

Hi Rob,

you are right if you define a date NOT NULL with DEFAULT the current date is
inserted.

I was in trouble because I always define the default as '0001-01-01' as
follows:
CREATE TABLE QTEMP/MYDATE2 
       (MYDATE DATE NOT NULL WITH DEFAULT '0001-01-01',
        ....

Birgitta

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von rob@xxxxxxxxx
Gesendet: Dienstag, 4. Oktober 2005 15:37
An: Midrange Systems Technical Discussion
Betreff: Re: AW: Dumb SQL question...

My earlier testing showed that on a NOT NULL WITH DEFAULT I got today's 
date.

You ought to see the @#$% I got with a simple NOT NULL:

drop table qtemp/donny

CREATE TABLE QTEMP/DONNY 
(MYCHAR CHAR ( 1) NOT NULL WITH DEFAULT,
MYDATE DATE NOT NULL) 

INSERT INTO QTEMP/DONNY (MYCHAR) VALUES('a')
Not authorized to object DONNY in QTEMP type *FILE.

Special authority  . . . . . . . . . . . . :   *ALLOBJ 
                                               *AUDIT 
                                               *IOSYSCFG
                                               *JOBCTL 
                                               *SAVSYS 
                                               *SECADM 
                                               *SERVICE 
                                               *SPLCTL 

Evidently IBM is totally off their nut.  Probably a QTEMP issue.  Let me 
retry:
drop table qtemp/donny
CREATE TABLE rob/DONNY 
(MYCHAR CHAR ( 1) NOT NULL WITH DEFAULT,
 MYDATE DATE NOT NULL)

INSERT INTO rob/DONNY (MYCHAR) VALUES('a') 
Null values not allowed in column or variable MYDATE.

Rob Berendt