Re: Oracle 7.3 not Y2K compliant on Digital Unix?

Eric Junkermann wrote:

> On 4 May 1998 14:38:12 GMT, "Saad Ahmad" <saad.ahmad_at_mchugh.com>
> wrote:
>
> >They might be referring to issues like:
> >SYS SQL> desc v$transaction
> > Name Null? Type
> > ------------------------------- -------- ----
> > ADDR RAW(4)
> > XIDUSN NUMBER
> > XIDSLOT NUMBER
> > XIDSQN NUMBER
> > UBAFIL NUMBER
> > UBABLK NUMBER
> > UBASQN NUMBER
> > UBAREC NUMBER
> > STATUS VARCHAR2(16)
> > START_TIME VARCHAR2(20) <<<------
> >
> >SYS SQL> update dual set dummy = dummy;
> >SYS SQL> select start_time from v$transaction;
> >START_TIME
> >--------------------
> >05/04/98 09:38:03
> >SYS SQL> rollback;
> >
> >But I won't sweat over it.
> >
>
> This is **not** a Y2K issue - selecting a date field from anywhere
> gets you the default format (which defaults to 2 digit year but can be
> changed) unless specified otherwise. If you want a 4-digit year,
> specify it and it will be correct.
>
> To go back to the original post, a 3rd party supplier is no more
> likely to be right than anyone else. Ask them for their reasons, and
> then get them independantly evaluuated (here would be good).
>
> Regards,
>
> Eric

 The START_TIME column is a VARCHAR2 and not a date. So maybe this is the Y2K issue.

--
*************************
Gary Smith
CERN, Geneva, Switzerland
Email: Gary.Smith_at_cern.ch
Tel:   +41 22 7678944
*************************