Hi,
I have a task to migrate H2 db into Postgres DB and found some not constant
behavior of timestamp fields when data is read. There are 2 columns, one
with summer time (DST on) and on with winter time (DST off). This is how
those are rendered when system's time zone is set to UTC: 2022-07-14
08:23:51.836 and 2022-11-24 04:04:25.822
And this is how it looks like in different time zones (DST on and off):
Timezone DST ON
DST OFF
Europe/Amsterdam, UTC+1 2022-07-14 09:23:51.836
(where DB was created) 2022-11-24 04:04:25.822
-----------------------------------------------------------------------------------------------------------------------------------------
Europe/Kyiv, UTC+2 2022-07-14 08:23:51.836
2022-11-24 03
:04:25.822
-----------------------------------------------------------------------------------------------------------------------------------------
Asia/Volgograd, UTC+3
2022-07-14 07:23:51.836
2022-11-24 03:04:25.822
----------------------------------------------------------------------------------------------------------------------------------------Asia/Bagdad,
UTC+3 2022-07-14 08:23:51.836
2022-11-24
04:04:25.822
----------------------------------------------------------------------------------------------------------------------------------------
Asia/Singapore, UTC+8
2022-07-14 08:53:51.836
2022-11-24 04:34:25.822
When debugging of org.h2.table I can see that timestamp consists of 2
parts: date and time. But when I do the conversion with H2 code, I can see
that those values are already adjusted depending on which time zone the
system is. The question is why it is not consistent with UTC offset of the
time zone? Is there any algo on how to calculate this adjustment?
Thanks!
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/h2-database/d8da729d-a51b-4207-97fe-418ed7ec5b93n%40googlegroups.com.
