Re: Dates, Y2K and Oracle 8 - question

Right, with a date format 'DD-MM-YY' Oracle is assuming the year being in the current century which will terminate in about 200 days. The interesting question is what Oracle will assume in the next century with the same date format?

Will it be the current century of the system date, i.e, 20YY? or 19YY

Okana schrieb:

> VB5
> Oracle 8.4 and 8.5
> ADO
>
> I use an Update SQL statement and execute the command. (I do not open a
> recordset) The only way I have found to update date fields in this manner
> is to pass the string configuration (dd-mmm-yy) in the update statement.
>
> Problem - Dates passed this way are being evaluated wrong when they hit
> Oracle - 2003 now becomes 1903, etc. I thought that Y2K compliance standard
> dictated that any two digit year less than 35 be automatically evaluated as
> 20xx. Oracle is not doing it this way. (Stupid assumption on my part)
>
> So - my big question is, if I do an update SQL statement is there a way to
> pass a date value with a four digit year in the statement or am I going to
> have to open recordsets to update any date to assure Y2K compliance?
>
> And as a side note - why is Oracle8 not Y2K compliant in this area?
>
> Michael Milliron
> mikem_at_msamail.com
> okana_at_msn.com

--
P.S: I am moving the e-mail account. Please use my new e-mail address as of now:

bmlam_at_online.de

May I also suggest that you update your address book accordingly if you are using one at all.

Received on Tue May 25 1999 - 16:41:52 CDT