On 2019-06-14 19:12, Lester Caine wrote:
On 14/06/2019 16:22, Mark Rotteveel wrote:
While implementing this feature in Jaybird I even considered using the
approach used by the PostgreSQL JDBC and that was simply always using
the UTC time and not even bothering with the offset and region
information.
PostgreSQL's built in timezone handling just does not work anyway!
The key factor here is that the ONLY reason for using timezones is to
provide a world agnostic time base. Firebird works PERFECTLY in this
world if the bog standard server installation is running on a UTC
based clock. The CLIENT displays IT'S local time or the time at an
alternate location. It is the location identifier that returns the
correct set of rules for the time you want to DISPLAY. And that may or
may not originate from the database. Eliminating any errors convert
BACK to UTC when the rule set may not be cleanly identified. This was
time zone 101 20+ years ago and nothing has changed since ... if you
ONLY want local time then just use that instead of UTC and ignore the
DST overlap problems.
Feel free to continue to use the old without time zone types.
Mark
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
