Issue Details (XML | Word | Printable)

Key: JDBC-629
Type: Sub-task Sub-task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: Mark Rotteveel
Votes: 0
Watchers: 0
Operations

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

Use 2020-01-01 for derivation of OffsetTime of TIME WITH TIME ZONE value with named zone

Created: 18/Jul/20 10:44 AM   Updated: 11/Aug/20 02:38 PM
Component/s: JDBC driver, XCA/JCA layer
Affects Version/s: Jaybird 4.0.0
Fix Version/s: Jaybird 4.0.1, Jaybird 5


 Description  « Hide
Firebird 4 just before beta 2 changed how it derived the base UTC time for a named zone, by always using 2020-01-01. To make sure values in Jaybird are consistent, it must also use 2020-01-01 when deriving the value of a java.time.OffsetTime. Do be aware that this means the derived offset value is as it applies at 2020-01-01, so for example '20:58:00 Europe/Amsterdam' will be '20:58:00+01:00', even if the value is derived on a date during summertime. Especially when using CURRENT_TIME, this may yield confusing results.

See also jdp-2020-06 OffsetTime derivation for named zone (https://github.com/FirebirdSQL/jaybird/blob/master/devdoc/jdp/jdp-2020-06-offsettime-derivation-for-named-zone.md)

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.