On 2017-11-21 17:16, Lester Caine wrote:
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 ...
If you need that, you also need to store the actual timezone somewhere.
PostgreSQL for example also uses an offset for timestamp with timezone
(not sure if that is required by SQL standard though).
Mark
------------------------------------------------------------------------------
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
