Hi, What version of H2 do you use?
> changing the Timezone on their computers. It shouldn't be a problem any longer. Could you tell me from what timezone to what new timezone the server was changed, and what date was problematic, so I can reproduce the problem? > it has been stated that the only way to represent > time points unequivocally is to store them as milliseconds from unix epoch in > the UTC. That was how H2 stored dates in older version, but it was very problematic (exactly because of problems when changing the timezone). > Check out joda-time for a better alternative While I agree the java.util.* date API is not nice, and the implementation is slow, I think that Joda-time will not actually solve the given problem. Also, java.sql.* still uses the java.util.* date API. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
