Hello Thomas and Rami, @Rami: You are right about java's bad handling of Dates and Calendar and I am aware of JodaTime but we need to stay as close to the standard as possible, plus we do not really care about the Timezone to be stored. All we need is for the UTC time to be properly stored in/loaded from the database irrespectively of the timezone and from then on we apply the correct DateFormat in order to display the values to the users.
@Thomas We are currently at version 1.3.155 and from what I see in the trunk the code still uses the ZONE_OFFSET although you have now promoted it to a constant. I will try and produce a test case for you. >> 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). I really do not see how this will be problematic. The UTC time should always be the same no matter the Timezone used. The only difference is when displaying the dates, at which point is where the application has to use the proper Timezone and Locale settings in order to display the value properly to the user. -- 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.
