Hello. It looks like you use some outdated version of H2, because MVCC setting doesn't exist in recent releases.
PostgreSQL doesn't have the NUMBER data type, and this type is not a native type of H2 too, why you use it? It is from Oracle, H2 accepts it, but only for compatibility with Oracle. It will not work in the real PostgreSQL. You need to use NUMERIC(6, 2) instead and yes, trailing zeroes should be here. Behavior of Oracle is incorrect. TIMESTAMP data type doesn't have a time zone. In H2 it is a local timestamp (in Oracle possibly too, but I don't remember it well). TIMESTAMP in PostgreSQL is an local, but UTC-based timestamp. Its local value will be changed if time zone of the session will be changed. There is a TIMESTAMP WITH TIME ZONE data type for absolute timestamps. Oracle and H2 preserve the time zone, PostgreSQL, unfortunately, doesn't preserve it and it returns timestamp in local time zone (but at the same absolute point in UTC). -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/1f560b2d-77c6-452a-b7e0-66c08431433f%40googlegroups.com.
