Re: how to set seconds-precision for systimestamp

From: Ken Quirici <kquirici_at_yahoo.com>
Date: Mon, 20 Apr 2009 15:48:21 -0700 (PDT)
Message-ID: <efd43e89-d76b-49ae-a68a-e1c32d4aa082_at_37g2000yqp.googlegroups.com>

On Apr 20, 2:05 pm, Frank van Bortel <frank.van.bor..._at_gmail.com> wrote:
> Ken Quirici wrote:
> > On Apr 19, 8:56 pm, Phil H <phil_herr..._at_yahoo.com.au> wrote:
> >> This is mentioned in Note 602951.1 in Metalink.
>
> >> Oracle just reads the OS system clock, which under Windows gives the
> >> time down to milliseconds, according to the docs for the SYSTEMTIME
> >> structure.
>
> >> -- Phil
>
> > Darn. Thanks for the info tho!
>
> I thought it was just the default (ff3, that is)
> Er... no it isn't:
>
> SQL> select systimestamp from dual;
> SYSTIMESTAMP
> ---------------------------------------------------------------------------
> 20-APR-09 08.01.35.719206 PM +02:00
>
> SQL> /
> SYSTIMESTAMP
> ---------------------------------------------------------------------------
> 20-APR-09 08.01.39.416713 PM +02:00
>
> SQL> /
> SYSTIMESTAMP
> ---------------------------------------------------------------------------
> 20-APR-09 08.01.40.549427 PM +02:00
>
> SQL> /
> SYSTIMESTAMP
> ---------------------------------------------------------------------------
> 20-APR-09 08.01.41.275923 PM +02:00
>
> --
>
> Regards,
> Frank van Bortel

I think it has to do w/ Windows as Phil said- when I do the above select systimestamp
from dual I get 6 digits of precision but the last 3 are zero - always. Received on Mon Apr 20 2009 - 17:48:21 CDT