Re: Problem with 02/29/2000
MJ
The problem definitely does not occur on my system. Here is a test script which
proves it.
I tested out the following script (myscript.sh) on my system (7.30.UC8) here.
Here is the script:
1 #!/bin/sh
2 onstat -V
3 echo $DBCENTURY
4 dbaccess spal_agg <<EOF
5 drop table test;
6 create table test (tdate date);
7 insert into test values ("02/29/2000");
8 insert into test values ("02/29/1900");
9 insert into test values ("02/29/00");
10 select * from test;
11 EOF
running the script:
prompt>./myscript.sh >myscript.out 2>&1
produced the following results:
Informix Dynamic Server Version 7.30.UC8 Software Serial Number AAC#J403635
C
Database selected.
Table dropped.
Table created.
1 row(s) inserted.
1206: Invalid day in date
Error in line 1Near character position 37
1 row(s) inserted.
tdate
02/29/2000
02/29/2000
2 row(s) retrieved.
Database closed.
As you can see, it barfs when fed 02/29/1900 (which is the same as 02/29/00 with
DBCENTURY
unset), but works with 02/29/2000 and 02/29/00 with DBCENTURY=C. Unsetting
DBCENTURY
gives me the same result (in this case the 02/29/00 means 02/29/2000).
HTH
Sujit
"M.J. Holley" <datashark@fastlane.net> on 02/26/2000 07:00:42 AM
Please respond to "M.J. Holley" <datashark@fastlane.net>
To: informix-list@iiug.org
cc:
Subject: Re: Problem with 02/29/2000
Sujit:
I am running 7.31 and I have the same bug with 2/29/00.
MJ