so apparently the java.sql spec says when you insert dates they automatically get converted to the default time zone of the jvm

which seems insane to me

is this just something people know to work around and set the default timezone of the jvm to utc on startup?

or am i missing something

Yup, it is both insane and something that people know to work around 🙂 The best practice is to set the TZ of every single server you use to UTC, set the database to UTC as well (if needed), and set the JVM TZ to UTC (again, if needed). Then convert to/from local time just at the edges, for display / input purposes only.

sigh well now i know i guess

i mean we were being good and using utc everywhere

but my jvm was running with the timezone of my laptop of course

just so crazy to see a value change between when java.jdbc/to-sql-value creates it and postgres gets it

wtf java.sql

My solution to that is to run a REPL on the production server and connect to it from my dev box -- so I'm working in UTC, even from my own machine 🙂

(just to run SQL stuff)

i mean i'm just gonna add a call to TimeZone/setDefault to the service skeleton for all our stuff

But, yeah, this bites me sometimes when I'm running Percona in Docker on my desktop and my JVM running the tests is on Pacific time. I try to not insert JVM-created dates, as much as possible and use SQL's NOW() and DATE_ADD()/`DATE_SUB()` where I can.

yeah good advice

i was just trying to insert a birth date haha

anyway, thanks for confirming its the world that is crazy and not me

I can neither confirm nor deny your sanity. I can, however, confirm the world is crazy.