Re: Y2K question

That's not a problem at all if you are totally OK with Oracle converting it to the same century as the system date (I think that's what it'll do), but the author of that quote is assuming that you won't always want that. If that's the case, yes - it is naturally a problem by the very nature of it and probably also would on any other system where you aren't specifying a 4-digit year and the system has a default way of handling that rather than erroring altogether.

Unless I'm missing something here too about your question...? --
Matt Brennan
SQL*Tools Specialist
GERS Retail Systems
9725-C Scranton Road
San Diego, California 92121
1-800-854-2263
mbrennan_at_gers.com
(Original email address is spam-blocked.)

Dave Morse <dmorse_at_nospam.cinergy.com> wrote in article <6q80um$fq3$1_at_news.iquest.net>...
> I recently read a quote in a publication that said:
>
> "And then, of course, there is the dreaded Year 2000 problem in Oracle.
If
> your code contains lines like this: v_mydate := TO_DATE(v_mystr,
> 'mm/dd/yy'); -- then you have some big problems coming down the pike."
>
> Do you agree? The TO_DATE function converts strings to the default
system
> date. In the above example, the 'mm/dd/yy' is simply telling Oracle what
> format the string 'v_mystr' is in, not what to convert it to.
>
> --
>
> Dave
> dmorse_at_cinergy.com (** please remove the 'nospam' from the address **)
>
>
>
Received on Tue Aug 04 1998 - 17:28:01 CDT