Bind time with time zone to legacy produces wrong values
--------------------------------------------------------
Key: CORE-6271
URL: http://tracker.firebirdsql.org/browse/CORE-6271
Project: Firebird Core
Issue Type: Bug
Affects Versions: 4.0 Beta 2
Reporter: Mark Rotteveel
Today, 29-03-2020, DST went into effect for my time zone (Europe/Amsterdam),
using legacy time zone results in wrong values for TIME WITH TIME ZONE values.
For example
D:\DevSoft\FB_tests\Firebird-4.0.0.1820-0_x64>isql
Use CONNECT or CREATE DATABASE to specify a database
SQL> connect 'localhost:employee' user sysdba password 'masterkey';
Database: 'localhost:employee', User: SYSDBA
SQL> set bind of time with time zone to legacy;
SQL> select CURRENT_TIME, LOCALTIME from RDB$DATABASE;
CURRENT_TIME LOCALTIME
============= =============
12:40:09.0000 13:40:09.0000
SQL>
I would expect that CURRENT_TIME and LOCALTIME to yield the exact same value in
this case.
This incorrect behaviour only occurs on the date of the DST change: after
changing my computer date to tomorrow (30-03-2020), both had the same value.
--
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
