For example, here is one worry I get from the PostgreSQL documentation <http://www.postgresql.org/docs/9.4/static/datatype-datetime.html>:
When a timestamp with time zone value is output, it is always converted from UTC to the current timezone zone, and displayed as local time in that zone. To see the time in another time zone, either change timezone or use the AT TIME ZONE construct (see Section 9.9.3 <http://www.postgresql.org/docs/9.4/static/functions-datetime.html#FUNCTIONS-DATETIME-ZONECONVERT> ). I interpret this to mean that, unless jOOQ uses AT TIME ZONE (specifying UTC) when querying the value, the value, even though *stored* in terms of UTC, would be converted to some arbitrary (depending on the current timezone zone) time zone before being converted to an absolute time value (analogous to Instant). So does jOOQ do the appropriate conversions to ensure that the Timestamp I store and the Timestamp I retrieve will always contain the same absolute time value, regardless of the system or database timezone in use? -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
