RE: SQL loval date/timestamp

I almost understand the difference, Buck.  You are correct, '0001-01-01' is
not null. 
However, when we display the column that does have a null value, the display
shows '0001-01-01'.  
Since there seemed to be no response to Joel's post yesterday, I thought I
would share what we loaded as low value.  

-----Original Message-----
From: Buck [mailto:buck.calabro@xxxxxxxxxxxx]
Sent: Tuesday, October 07, 2003 11:55 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: SQL loval date/timestamp


> When using Date fields in SQL defined tables, we
> have set the *loval at '0001-01-01'.
> This seems to be null in the table then.

*LOVAL and NULL are not the same thing.  There is no field value which means
NULL.  In order for a field to be NULL, one must set the null indicator or
the appropriate null map.  I realise the request does not mention NULL, but
felt compelled to respond to this post.  NULL is not a value, it is an
attribute like size and text.
  --buck



_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.