Re: Problem with result set from a simple SQL Select

From: Malcolm Dew-Jones <yf110_at_vtn1.victoria.tc.ca>
Date: 30 Jan 2005 13:56:27 -0800
Message-ID: <41fd580b_at_news.victoria.tc.ca>


[Quoted] [Quoted] IANAL_VISTA (IANAL_Vista_at_hotmail.com) wrote:
: "lennyw" <lwintfeld_at_libertycorner.net> wrote in
: news:1107044827.490858.34650_at_f14g2000cwb.googlegroups.com:

: > Thanks for your reply. I'll add the TO_DATE to the query when I get
: > back to work on Monday. You're right that a DATE type is not a string;
: > it's an integral multiple of milliseconds since <some epoch>.

: SELECT TO_CHAR
: (SYSDATE, 'MM-DD-YYYY HH24:MI:SS') "NOW"
: FROM DUAL;

: A DATE datatype only provides granularity down to 1 second intervals.

: Oracle can store dates in the Julian era, ranging from January 1, 4712 BCE
: through December 31, 4712 CE (Common Era, or 'AD'). Unless BCE ('BC' in the
: format mask) is specifically used, CE date entries are the default.

[Quoted] Newer versions of Oracle appear to have a date format mask for fractions of a second (.F?), from which I assume that the time resolution can be smaller than one second in those versions.

--

This space not for rent.
Received on Sun Jan 30 2005 - 22:56:27 CET

Original text of this message