Re: DBCENTURY not working on 7.24.UC1??

On 18 Aug 1998, David Samson wrote: > I was checking our Y2K compliance on 2 versions: 7.24.UC1 and 7.3.UC2 > (both HP-UX 10). In both cases, I set DBCENTURY = C (closest). I > tried to update a datetime field with the following SQL: > > update t1 > set d1 = '00-02-29 01:11:00' > > On 7.3, this worked fine. It assumed 29 Feb 2000. Yes; B60150 is fixed in 7.30. > On 7.24, I got a "1263: A field in a datetime or interval value is out of > range or incorrect." B60150 is only fixed in 7.24.UC4 or later. > Is this correct behavior? Shouldn't it assume 2000 for the statement on > all compliant versions (i.e. 7.20 and later)? If I was asked, I'd say that any 2-digit year in a datetime should apply to the first century AD, but I gather that 2-digit years are translated into 4-digit years with the addition of an appropriate century value. To enter the first possible datetime year to day value, you have to use 001-01-01 or 0001-01-01 to prevent the century being nobbled for you. Yours, Jonathan Leffler (jleffler@informix.com) #include <witticism.h> Guardian of DBD::Informix v0.60 -- http://www.perl.com/CPAN Informix IDN for D4GL & Linux -- http://www.informix.com/idn