Re: Oracle date/time precision

From: <pberetta_at_my-deja.com>
Date: Sat, 11 Dec 1999 12:24:24 GMT
Message-ID: <82tfpm$idj$1_at_nnrp1.deja.com>


Fred,

   The values stored in an Oracle DATE cannot have a precision greater than the nearest second. There are methods of retrieving more precise time values from the O/S, but you will need to either create a second column to store fractional seconds, or create a single column which will not be an Oracle DATE to store the entire string. Using either method (but probably easier with the second) you can then create a set of functions to make the conversions more transparent to the user. Perhaps if enough customers complain about this shortcoming, Oracle will consider adding a true TIMESTAMP datatype to a future release. Hope this helps,
Paul

In article <385044AA.B75039F2_at_avialantic.com>,   Fred Pierce <fpierce_at_avialantic.com> wrote:
> A customer requires values they supply to be stored in Oracle date
> columns to be precise to milliseconds. Oracle doesn't seem to have
that
> capability. Does anyone have any suggestions as to how this might be
> simulated?
>
> The obvious solution is to store the dates as strings and let the
> application do the conversion, but apparently the customer wants to be
> able to query the columns directly as dates.
>
> Thanks for any ideas.
>
> fdp
>
> --------------------------------------------------------------------
> Fred Pierce (DNRC)- fpierce_at_avialantic.com Oracle/Sybase DBA
> Mid-Atlantic Aviation on the Web - http://www.avialantic.com
> ** Mid Atlantic Air Museum *** World Airshow News **
> ---------------------------------------------------------------------
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Sat Dec 11 1999 - 13:24:24 CET

Original text of this message