On 02/06/2020 16:11, Mark Rotteveel wrote: > The recent changes to fix the derivation of TIME WITH TIME ZONE to > 2020-01-01 has weird consequences. In summer time, the value of for > example CURRENT_TIME is now off by 1 hour when looking at the UTC time > value. > > This leads to the following confusing results: > > SQL> set time zone 'Europe/Amsterdam'; > SQL> select current_time at time zone 'UTC' from rdb$database; > > AT > ============================================== > 20:08:36.0000 UTC > > SQL> set time zone 'UTC'; > SQL> select current_time at time zone 'UTC' from rdb$database; > > AT > ============================================== > 19:08:45.0000 UTC > > SQL> select current_time from rdb$database; > > CURRENT_TIME > ============================================== > 19:08:52.0000 UTC > > SQL> > > Maybe it is better if CURRENT_TIME doesn't use the named zone, but > instead always uses an offset based value. > I'm not sure it is. This would create other inconsistencies (cast(current_timestamp as time with time zone) <> current_time).
There is no problem with a time with zone, the problem is when one uses it to do things that depends on a date, like you did here. Documentation should be improved for this case too. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
