Hi,
I think you should write a simple, self contained, reproducible test case.
Regards,
Thomas
On Monday, July 24, 2017, marcolopes wrote:
> I believe H2 works differently from MySQL and PostgreSQL :
> LocalTime is not SAVED, so, i have a big problem in my
The problem is if the same database is opened in a different TIMEZONE, all
the DATE and TIME will be changed!!!
I cannot control if the fields were saved under ONE or another timezone!!
It is up to the database engine to do that...
TIME 00:00 saved under one timezone should be retrieved as
How the data is presented is up to you, we just make sure the same data is
stored and retrieved.
--
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
I explained myself wrong...
The DATE and TIME must be presented the same way if the database is
accessed in another timezone! So, original timezone must be taken into
account...
On Sunday, July 23, 2017 at 6:52:58 AM UTC+1, Noel Grandin wrote:
>
> our DATE/TIME fields very specifically do not
our DATE/TIME fields very specifically do not change across time zones.
But if other layers are converting backwards and forwards through types
like Timestamp, it is quite possible that they may influence the results.
--
You received this message because you are subscribed to the Google
I've been using H2 for years (stayed on version h2-1.3.169 because of
inconsistent behavior of the next 1.3.x versions)
Recently i've found a behavior that needed days of debug and is affecting
VERY SENSIBLE information: *the DATE / TIME types behavior across timezones
/ DST*?
I need a