On 11/05/2018 06:54, Lester Caine wrote: > I was having a proper look through the Oracle timezone documentation > and thinking 'how can you get it so wrong'. Does it REALLY have a > ERROR_ON_OVERLAP_TIME flag because it allows the server local clock to > be used raw. Actually this is no different to the current situation > without managing timezone at all since for those areas of the world > that do implement daylight saving there is an ambiguous hour every > year and most of the time it is simply ignored? Log files get > overlapping data and one lives with it? > Maybe you completely misunderstood it?
The thing about ambiguous times is only when converting from string to timestamp. Once it's converted, everything works. See my example to Vlad. So a given timestamp + 1 hour may return the same timestamp/tz, but with different displacements. I suppose we do not want to add to our timestamps the suffixes 'before dst ends' and 'after dst ends'. Adriano ------------------------------------------------------------------------------ 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
