On 11/05/18 16:07, Adriano dos Santos Fernandes wrote:
On 11/05/2018 11:55, Lester Caine wrote:
On 11/05/18 15:44, Adriano dos Santos Fernandes wrote:
If the machine clock goes back one hour because of a DST transition,
the current time overlaps and the same set of numbers are used twice.
No.
We are talking currently with a normal 64bit TIMESTAMP ...
The comparison with Oracle is that they use a simple TIMESTAMP where
possible and add the timezone information outside of the stored data.
Oracle has TIMESTAMP WITH TIME ZONE.
Which as I have said is of little use if you don't know what rule set
version was being used when the timestamp was stored! Only storing a
clean UTC timestamp will give you an accurate consistent time base.
Checking Postgres again, and as I thought, their 'with timezone' is
simply a offset stored with the original timestamp. So you have no idea
what 'timezone' was used to create it! So should not be called 'with
timezone'?
Just what is Firebird storing for the timezone element?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
