Re: Y2000 and 29/02/00~v

On Wed, 29 Oct 1997, Gavin Convery wrote: > Anybody else come across this problem? Not until you pointed it out. > If you are using a two digit year with DBCENTURY set to C and try and > insert the date 29/02/00 you will get a 1204 - Invalid year in date. I can confirm that for OnLine 7.23.UC1 on Solaris 2.5.1. > Neat, huh?!? Not in my book. The error message doesn't make sense. Invalid day in date would be explicable -- the conversion to 4-digit year was taking place after the leap year check. I suppose it could be that they are taking the 2-digit year (00) and treating is as a 4-digit year before doing the addition; then it is an invalid year (there was no year 0; it went 1 BC to 1 AD). > Apparently Informix don't consider this a high priority problem. Do you have support? If so, get it entered as a bug. It is a bug, but if I enter it, it is an incredibly low priority bug, simply because I'm not a customer. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h>