Re: oracle timestamp internal storage and precision
From: Tim Gorman <tim_at_evdbt.com>
Date: Wed, 19 Dec 2012 12:07:14 -0700
Message-ID: <50D21062.1040802_at_evdbt.com>
When you say "internal timestamp" and "number", are you referring to DATE and TIMESTAMP data types, or are you referring to the SCN (i.e. system change number) used internally within the RDBMS as a relative timestamp? The wording of the question could go either way...
Date: Wed, 19 Dec 2012 12:07:14 -0700
Message-ID: <50D21062.1040802_at_evdbt.com>
When you say "internal timestamp" and "number", are you referring to DATE and TIMESTAMP data types, or are you referring to the SCN (i.e. system change number) used internally within the RDBMS as a relative timestamp? The wording of the question could go either way...
On 12/18/2012 5:49 PM, Walker, Jed S wrote:
> I could swear that a while back I read or saw a presentation from someone where they discussed how Oracle stores the internal timestamp. They said it was stored as a number and that in order to not expire to early (like UNIX time) the storage would, over time, sacrifice sub-second precision to extend the date range. I tried searching for this, but have found nothing. I wonder if I'm remembering wrong, or if maybe it just isn't something that has been published.
> Do any of the Oracle internal experts out there know?
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Dec 19 2012 - 20:07:14 CET