RE: SQL loval date/timestamp

["Scott Johnson" <sjohnson@xxxxxxxxxxxxx>]

'0001-01-01' is NOT null.  '0001-01-01' is a valid date.  Null can be the
indication of missing data.  Shipping date on a new order is a good example.  If
the field is Null capable, then use Null.  What confuses people is that DB2
still requires a valid date in the field.

With that said, initial value for timestamp can be '0001-01-01-00.00.00.000000'.

-- Scott J

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Dave Boettcher
> Sent: Tuesday, October 07, 2003 11:37 AM
> To: 'RPG programming on the AS400 / iSeries'
> 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.
> Have not used the timestamp fields.
>
> HTH,
>
> Dave Boettcher
>
> -----Original Message-----
> From: Joel Cochran [mailto:jrc@xxxxxxxxxx]
> Sent: Monday, October 06, 2003 6:00 AM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: SQL loval date/timestamp
>
>
> Can anyone tell me what the acceptable *loval for SQL Date
> and Timestamp
> would be?
>
> Thanks,
>
> Joel
> http://www.rpgnext.com
>
>