Re: Internal Date Issue

This seems entirely plausible.
It would be useful to check what happens when you try to view the date with a YYYY format, though.

For the record, I have managed to get impossible dates out of Oracle (such as '00-Dec-1987') when an OCI program has passed a date to Oracle as a 'guaranteed correct type 12 (internal date format)' value, but lied about the guarantee.

It is possible that you JDBC driver is doing the same sort of thing - i.e. making a call with incorrect data that bypasses some
internal validation routine.

--

Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk

J Mike Rollins wrote in message <85dsm3$p2c_at_f1n1.spenet.wfu.edu>...
>
>
>INTERNAL DATE_TIME
>----------------------------------- ---------
>Typ=12 Len=7: 119,200,1,3,9,51,1 03-JAN-00
>Typ=12 Len=7: 119,200,1,4,6,1,1 04-JAN-00
>Typ=12 Len=7: 119,200,1,4,10,2,1 04-JAN-00
>Typ=12 Len=7: 119,200,1,8,4,2,1 08-JAN-00
>Typ=12 Len=7: 119,200,1,9,18,4,1 09-JAN-00
>Typ=12 Len=7: 120,100,1,2,8,23,1 02-JAN-00
>Typ=12 Len=7: 120,100,1,3,5,1,1 03-JAN-00
>Typ=12 Len=7: 120,100,1,9,6,46,1 09-JAN-00
>
>This shows that there are two ways for storing y2k dates internally.
> Typ=12 Len=7: 119,200,1,3,9,51,1 03-JAN-00
> Typ=12 Len=7: 120,100,1,3,5,1,1 03-JAN-00
>
>The first 03-JAN-00 is stored as
> century = 100+19
> year = 100+100
>
>The second 03-JAN-00 is stored as
> century = 100+20
> year = 100+ 0
>
>And it seems that the "order by date" is sorting these according to
>the century first, and then the year.
>
>We think this might be due to an old classes111.zip JDBC drivers using
>the setDate function from a PreparedStatement.
>
Received on Tue Jan 11 2000 - 15:18:32 CST