Issue Details (XML | Word | Printable)

Key: JDBC-622
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: Mark Rotteveel
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
Jaybird JDBC Driver

Find way to address (or at minimum document) time abberation for TIME WITH TZ literals with zones

Created: 15/May/20 03:35 PM   Updated: 25/Jul/20 11:04 AM
Component/s: JDBC driver
Affects Version/s: Jaybird 4.0.0
Fix Version/s: Jaybird 4.0.1, Jaybird 5

Sub-Tasks  All   Open   

 Description  « Hide
Just before the Firebird 4 beta 2 release, the decision was made to base the UTC derivation for TIME WITH TZ literals with a named zone on 2020-01-01 instead of the current date. This causes off-by-one-hour issues with the logic in Jaybird to use the current-date for determining the offset for the named zone.

As an example, selecting time'13:25:32.1235 Europe/Amsterdam' on the 15th of May will now yield an offset time 14:25:32.123500+02:00 instead of either 13:25:32.123500+02:00 (older snapshots of Firebird 4), or 13:25:32.123500+01:00 (which would be inline with what Firebird derives).

Find a way to address this, or at least add a caution to the documentation.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel added a comment - 15/May/20 03:51 PM
Using 2020-01-01 as base date for offset derivation might be the best and most compatible option, however I have also raised a discussion on firebird-devel if we really want this.