Re: ok. I give up.

David

Unfortunately, the original poster required a resolution that is beyond that kept by the date datatype (to the millisecond). In this case, depending on what the requirement is you can either store the milliseconds as a separate number column, or if the purpose is to derive time from a specific event, the get_time function could be used instead which does allow millisecond resolution.

HTH. Pete

David Sisk wrote:

> Hi:
>
> Just make you column a date datatype. Take a look at the to_char function
> to see what you can get out of a date column.
>
> Regards,
>
> --
> David C. Sisk
> Need tech info on Oracle? Visit The Unofficial ORACLE on NT site at
> http://www.ipass.net/~davesisk/oont.htm
> Like original music? Listen to song samples and buy a CD at
> http://www.mp3.com/disparityofcult
>
> uncle.scrooge wrote in message <37AB8B37.476F2D65_at_worldnet.att.net>...
> >
> >Plain and simple : If I want to have a column that tracks the current
> >time in millisecond resolution,
> >can I do it or not? i.e. I want a timestamp, but second resolution is
> >too "gross". What do I do if I'm importing
> >data from a database that does have millisecond resolution in it's
> >columns (i.e. sybase)?
> >
> >
> >Do I need to create my own datatype or smth?
> >
> >pls help - thx
> >

--
Regards

Pete

Received on Mon Aug 09 1999 - 11:02:39 CDT