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 clarification, because i don't know what to do! I have several cryptographic methods that are based on DATE and TIME fields, and they expect these fields to return the EXACT same value that was stored. I give you and example: an INVOICE is stored in the database, with *DATE and TIME values that CANNOT change across timezones / DST...* Currently, this sensitive data is being adjusted accordingly the TIMEZONE / DST!!! This cannot happen!!! I really need help understanding this situation.. *this does not occur with PostgreSQL or MySQL DATE and TIME types...* How can i READ the DATE / TIME fields without timezone manipulation? This is very very important, because a document cannot be edited and worst, PRINTED! with different values! Thanks a lot! P.S. I'm using DataNucleus as a persistence layer. -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
