On 21/11/17 14:55, Adriano dos Santos Fernandes wrote: > Implementing TIME WITH TIME ZONE and TIMESTAMP WITH TIME ZONE datatypes > as specified in the SQL standard is not a big problem.
The only question is just how is the timezone data managed. It is useless simply having an offset value when large areas of the planet still use daylight saving. If I move a meeting from March to April I need to know the real timezone, a simple hour offset is no good at all. It's the same old problem as the offset provided by a browser ... useless for half of the year ... -- 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
