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
CustomDataTypeHandler already supports more then one new datatype.
--
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 h2-database+unsubscr...@googlegroups.com.
To
what does your H2 URL look like? Are you using the H2 JDBC driver?
If your app is heavily multi-threaded, you could try MULTI_THREADED=true,
which is almost production-ready
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from
I have a 3-tier setup (DB, webserver + app, driver) that I measure
performance on, and it usually uses DB2. I wanted to try H2 because DB2 is
painful to setup and H2 was dead simple.
I don't do much with or know much about databases, my concerns are mainly
in the other tiers, but after a bit
Hello,
Currently, in H2, we can implement one custom data type by implementing
CustomDataTypeHandler and setting the system
property h2.customDataTypesHandler to the class name that provides the
implementation of this interface.
Is there a provision in H2 where we could implement more than one
