We have an application here at my company that needs to perform several operations on some data by using its timestamp as a reference. I only now noted that a large part of the bugs found in the program are due to h2 loading the time zone from the machine I am running. I wish I could default h2 behavior to use a given timezone(GMT-3) while loading and providing the stored data. Ideally I should set the timezone to a specific table, but that is not needed.
To give an idea of what kind of problems I am having, here is the scenario: At the production envirnoment --- Application is at GMT-3 And make a query to the data in the interval [2011/01/01 00:00, 2011/01/02 00:00[ The server is at GMT And returns the data [2011/01/01 03:00, 2011/01/02 03:00[ The application than takes that data and uses the value returned AS IT IS(that means no timezone conversion) At the development environment I have: Application is at GMT-3 And make a query to the data in the interval [2011/01/01 00:00, 2011/01/02 00:00[ The server is at GMT-3 And returns the data [2011/01/01 00:00, 2011/01/02 00:00[ Well, thats it. How do I solve that? -- 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.
