I'm no SQL expert but I do know my way around Java times, dates, time zones, and Joda.
I saw several (old) discussions here and elsewhere about jOOQ problems with PostgreSQL TIMESTAMP WITH TIMEZONE, including https://github.com/jOOQ/jOOQ/issues/2738 . I don't know what the latest status is. I note that jOOQ takes a long absolute time value (which is independent of time zone by nature of its being locked to UTC---and equivalent to Java 8 Instant) to store a Timestamp in a TIMESTAMP WITH TIMEZONE column. When I query the value I get back a Timestamp, which again is equivalent (and convertible to) a Java 8 instant. So where does the time zone come in? Is WITH TIMEZONE really required in the type? And if I am saving and retrieving an absolute Instant equivalent (which is locked to UTC), why does the time zone matter? Basically I only care about time zones as far as retrieving the exact same absolute time value I started with. The most important question: if I use jOOQ to store a value in a TIMESTAMP WITH TIMEZONE using a Timestamp, and later if I connect from another time zone and request the Timestamp back, will I get the same absolute (UTC-relative) value I put in? -- 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.
