Hi Wes, Do you really need to store the time zone? It usually easier to use the standard datetime behaviour of storing in an internal format and then translate it to whatever timezone is appropriate to the viewer when the data is pulled out.
Are you sayng that if... - user A stores a record in the UK, and - user B stores a record in New Zealand ... you want user C (in Washington) to see times displayed in GMT and NZDT (not in Washington time, whatever that is) It usually makes it a lot easier to reconcile the data without dealing with timezones. Just wondering. Cheers Kerry On Tue, Nov 17, 2009 at 12:18 PM, Wes Clark <[email protected]> wrote: > Our application supports users across multiple time zones, so we are > facing a need to store timestamps/datetimes that have an associated > time zone. Oracle has TIMESTAMP WITH TIME ZONE, and SQL Server 2008 > has added datetimeoffset, and both of these appear to meet our needs. > DB2 doesn't have anything I can see. H2 doesn't sport anything along > these lines, does it? > > -- > > 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]<h2-database%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=. > > > -- 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=.
