On 2013-07-16 08:20, [email protected] wrote:
We are trying to move our product from Oracle to H2 database, but
there is a problem that in our product using TIMESTAMP WITH TIMEZONE
data type.
How does H2 database can support this kind of data type? Is there any
suggestion?
PS. I do found this before add this topic:
https://groups.google.com/forum/#!searchin/h2-database/TIMESTAMP$20with$20timezone|sort:relevance/h2-database/1obbL2vYHAg/kC02qYqa304J
<https://groups.google.com/forum/#%21searchin/h2-database/TIMESTAMP$20with$20timezone%7Csort:relevance/h2-database/1obbL2vYHAg/kC02qYqa304J>
But the date of this topic is 2009 I guess if there is any change on
h2 database to support this data type.
We don't support this datatype at the moment.
You'd probably need to either implement it yourself as a custom
datatype, using OTHER, or split it manually into a TIMESTAMP field and
another field to represent the timezone.
Personally, I think you're better off simply storing your data using a
normal TIMESTAMP date which stores these things as UTC internally.
Especially given that
(a) this datatype is not widely supported and
(b) the different databases (.e.g Oracle / PostgreSQL / MSSQL ) appear
to implement this datatype differently.
--
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/groups/opt_out.