Hi! I would very much like if H2 could support the (afaik *SQL standard)* datatype "TIMESTAMP WITH TIMEZONE". Also, for MS SQL compatibility, it would be *terrific* if this type had an alias called "DATETIMEOFFSET" *(MS SQL has totally mangled what the TIMESTAMP means, effectively meaning "rowversion", which with SQL Server 2000 also is an alias, where they say that they might later change the behaviour of timestamp to "to align it with the behavior defined in the standard.")*
Oracle impl.: https://docs.oracle.com/database/121/NLSPG/ch4datetime.htm#i1006081 Postgres impl.: http://www.postgresql.org/docs/9.1/static/datatype-datetime.html MS SQL Server DateTimeOffset: SQL: https://msdn.microsoft.com/en-us/library/bb630289.aspx .Net: https://msdn.microsoft.com/en-us/library/system.datetimeoffset(v=vs.110).aspx Note how Postgres uses a very simple implementation (IIUIC): It just uses the offset to calculate the UTC value which it stores, and then upon select adjusts it back to the *server* timezone offset. Thus, you will not necessarily get the actual stored TZ offset back when you select, and if you change the world location of the server (change TZ, that is), then you will get a different offset back - *but the timestamp will nevertheless still represent the same instant on the world timeline* - so it is "better than nothing". Could this be considered? Thanks a bunch, Kind regards, Endre. -- 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.
