Informix 4.10 leap year problem
The Informix 4.00 system that I am working on runs on a Unix box that is correctly abiding by leap-year rules. On typing the SQL command; select date(today) from systables all the dates returned are incorrect i.e. 2/3/2000 and users say that yesterday all of the date fields that were meant to be showing today's date were showing 1/3/2000 not 29/2/2000 When inputting into datefields was previously tested the software was compliant - accepting 29/2/2000 and not 29/2/1999. How or from where do the informix application work out the TODAY variable. Sent via Deja.com http://www.deja.com/ Before you buy.
Now you know why Informix has been telling the world via its Y2K web page that only 4.20 I4GL and 5.10 OnLine or SE is Y2K-compliant. Neither 4.00 nor 4.10 is -- as you have found out. Time to upgrade!!! (One exclamation mark for each time I've given this explanation so far this evening). humbeast@my-deja.com wrote: > The Informix 4.00 system that I am working on > runs on a Unix box that is correctly abiding by > leap-year rules. On typing the SQL command; > select date(today) from systables > all the dates returned are incorrect i.e. 2/3/2000 > and users say that yesterday all of the date > fields that were meant to be showing today's date > were showing 1/3/2000 not 29/2/2000 > When inputting into datefields was previously > tested the software was compliant - accepting > 29/2/2000 and not 29/2/1999. > How or from where do the informix application > work out the TODAY variable. > > Sent via Deja.com http://www.deja.com/ > Before you buy. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.95 -- see http://www.perl.com/CPAN #include <disclaimer.h>
Jonathan: I think that most people know that versions 4.1x and prior are not Y2K compliant. I suspect that since it worked ok after Jan 1, that people did not properly test for 2/29. The real question being asked though, is there a workaround? An example might be: Set the Unix Date back one day. or change all of your occurances of 'today' in your code to 'today - 1' (yes, both of which are nasty...) Or is there a 'magic pill' (patch) to create a workaround for the problem Some groups of people simply do not have the resources to upgrade their Informix software. So does anyone have any ideas or to the original posters question: Where does the TODAY come from within Informix... And does anyone have a workaround... Jonathan, this is NOT intended as a flame, I have the utmost respect for your opinions, just an alternate view of where people are coming from. Rick
What irritates me isnt so much the cost of the upgrade as the fact I am forced to buy it with a years software support contract that I dont want and dont need. I think the last time I upgraded it cost me '1800 for the upgrade and an extra 1200 quid for nothing. Keith "Risudi" <risudi@aol.com> wrote in message news:20000302024610.01244.00003210@ng-xe1.aol.com... > Jonathan: > I think that most people know that versions > 4.1x and prior are not Y2K compliant. I > suspect that since it worked ok after Jan 1, > that people did not properly test for 2/29. > > The real question being asked though, > is there a workaround? > > An example might be: > Set the Unix Date back one day. > or change all of your occurances of > 'today' in your code to 'today - 1' > (yes, both of which are nasty...) > > Or is there a 'magic pill' (patch) to > create a workaround for the problem > > Some groups of people simply do not have the resources to upgrade their > Informix software. > > So does anyone have any ideas or to the original posters question: > Where does the TODAY come from > within Informix... And does anyone have a workaround... > > Jonathan, this is NOT intended as a flame, I have the utmost respect for your > opinions, just an alternate view of where people are > coming from. > > Rick >