Hi, I suggest to read and maybe debug the source code of H2 to understand how things work currently. If possible, use examples in source code form so we can easier understand what you mean.
> To me it would seem that the most portable format is the first one I > mentioned that has no ambiguities and is the most compact format available. Which one is the first you mentioned? > As I mentioned when using prepared statements one is in full control over > that. I don't understand. > Now if I start the h2 jvm with a different default timezone then I suppose > that when reading timestamps > they are formatted to string literals using the timezone that was associated > at insert/update time. I guess you have to read the source code of H2. Timestamps are written and read in the class Data.java, writeValue() / readValue(), case case Value.TIMESTAMP. > Where does the timestamp initially (at insert time) get it's timezone? > I'm quessing from jvm's default timezone. > Now if I start the jvm with a different timezone and update the timestamp is > the timezone updated? The timezone is not stored. > And timezone info in java.sql.Timestamp is deprecated and invalid. There is no timezone info in java.sql.Timestamp. 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.
