I also think that since the documentation of the Timestamp class does NOT make any reference on Timezones and since java.util.Date specifically states that the value is ALWAYS GMT then the developer should NOT expect the Timezone value stored in a Timestamp column.
I can see the following workarounds for handling timezones: 1) The application developer should use an extra column for storing the Timezone and apply any needed changes manually 2) The database could have a system property for the timezone( I think oracle works this way) and H2 apply it always 3) Have an extra composite custom H2 data type that can handle both timestamp and timezone. What do you think? -- 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.
