oracle timestamp internal storage and precision
From: Walker, Jed S <Jed_Walker_at_cable.comcast.com>
Date: Wed, 19 Dec 2012 00:49:45 +0000
Message-ID: <BAA6E28B6241F046AED1E62D8697516C6F5AF591_at_COPDCEXMB08.cable.comcast.com>
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?
Date: Wed, 19 Dec 2012 00:49:45 +0000
Message-ID: <BAA6E28B6241F046AED1E62D8697516C6F5AF591_at_COPDCEXMB08.cable.comcast.com>
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 - 01:49:45 CET