OK, so I can see that timestamps will remain the way they are in H2. That's perfectly fine. Obviuosly, Thomas has given this some deeper thought - I, myself tend to avoid wrapping my mind around that dreaded subject ;-)
But going back to the original issue, what would be the optimal way to: - store timestamp values - read java.sql.Timestamp values If you would be storing timestamp literals as strings (as Thomas suggested at some point), would Timestamp.valueOf(String) perform faster? Would it still retain the timezone calculations currently implemented in DateTimeUtils? Cheers Lukas 2014-05-06 21:04 GMT+02:00 Rami Ojares <[email protected]>: > Well, frankly I am ok with any approach since I already use succesfully > the biggint type and custom made functions for all my temporal needs. > I merely wanted to give my thoughts as a service to the community. > And completely respect your views as the owner of this project. > > Sincerely, > Rami > > -- > You received this message because you are subscribed to a topic in the > Google Groups "H2 Database" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/h2-database/nZFJHNdbS3o/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
