Use of timestamp or time with TZ is inconvenient for users when appropriate ICU
library is not installed on a client
--------------------------------------------------------------------------------------------------------------------
Key: CORE-6286
URL: http://tracker.firebirdsql.org/browse/CORE-6286
Project: Firebird Core
Issue Type: Improvement
Components: API / Client Library, Engine
Affects Versions: 4.0 Beta 1
Reporter: Alexander Peshkov
Time (or timestamp - please keep it in mind here) with TZ is always sent to
client using GMT. TZ information may be represented as offset (in that case
converting GMT time to local one is not a problem) or zone code, and in this
case mentioned conversion is problematic. Client library when can not convert
GMT to local time is displaying time in original GMT form. People hate that
behavior - they want to be able to get time in a zone as it was entered by
default.
In order to solve that problem format extension is suggested - EXTENDED TIME
WITH TIME ZONE. That form will have additional 2-byte field where offset of
time zone is always placed by DB engine. Conversion of such datatype to local
time on client is always trivial. The only place where that datatype may be
used is SET BIND statement. To make things a little more flexible a generic
'EXTENDED' pseudo-datatype is also introduced as a target of SET BIND. When
it's used (as target) an EXTENDED form of source datatype of SET BIND will be
used as target.
And to make it even more flexible 'TIME ZONE' pseudo-datatype should be usable
as source type of binding. When it's found in SET BIND that should make such
SET BIND match any datatype containing time with time zone.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel