Re: Y2K Date Issues with Oracle 7.3.4
Date: Sat, 15 Jan 2000 21:06:31 +0200
Message-ID: <85qgh1$2nf2$1_at_ulysses.noc.ntua.gr>
[Quoted] interesting fact:
[Quoted] [Quoted] If you cast "to_date" a date variable (don't ask me why you would like to do that), then no matter how much care you took in placing the correct date in the variable, the result will be a date after 2000.
For example
[Quoted] a_date DATE;
a_date := to_date('12/10/1998','DD/MM/YYYY'); a_date := to_date(a_date);
now a_date has a 12/10/2098 value!
Steve McDaniels <steve.mcdaniels_at_sierra.com> wrote in message
news:85lnet$lki$1_at_plo.sierra.com...
> We simply use 'YYYY' in all date conversions
>
> to_date('01-JAN-1999','DD-MON-YYYY')
> and
> to_char(sysdate,'DD-MON-YYYY')
>
>
>
> Mungo Henning <mungoh_at_itacs.strath.ac.uk> wrote in message
> news:387DE3D7.B44F28B1_at_itacs.strath.ac.uk...
> >
> >
> > James Lorenzen wrote:
> >
> > > [good stuf snipped]
> >
> > Just a little warning: remember that the RR format is fine for "recent"
> > dates,
> > but if you have anyone born before 1950 (data for insurance policies
etc)
> > then the RR format will give you grief when it interprets "49" as
"2049".
> >
> > Mungo
> >
> > --
> > Mungo Henning - it's a daft name but it goes with the face...
> > mungoh_at_itacs.strath.ac.uk.http://www.itacs.strath.ac.uk/
> > I speak for me, not my employer.
> >
> >
>
>
Received on Sat Jan 15 2000 - 20:06:31 CET