On 2017-11-21 15:55, Adriano dos Santos Fernandes wrote:
Hi!
Implementing TIME WITH TIME ZONE and TIMESTAMP WITH TIME ZONE datatypes
as specified in the SQL standard is not a big problem.
However, standard says that CURRENT_TIME / CURRENT_TIMESTAMP returns
the
timed-zone datatype.
That causes two problems:
- Internally (say in PSQL), conversion to string would return different
result than now
- Externally, tools will take time to support this datatype
The others DBMS seems to follow the standard (probably since they
introduced these constructions).
Do you see a good way to workaround this issue?
Maybe have a similar option as with the DECFLOAT support. That is, to
have a session config that determines the return type current_time and
current_timestamp, but also have a config option that can set a default
per database?
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
