This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-15
Channels
- # adventofcode (6)
- # beginners (63)
- # boot (39)
- # cider (25)
- # clara (9)
- # cljs-dev (27)
- # clojure (100)
- # clojure-dev (39)
- # clojure-dusseldorf (7)
- # clojure-italy (32)
- # clojure-russia (23)
- # clojure-spec (28)
- # clojure-uk (51)
- # clojurescript (197)
- # core-async (44)
- # cursive (3)
- # datomic (14)
- # emacs (4)
- # fulcro (27)
- # graphql (23)
- # hoplon (4)
- # jobs (9)
- # juxt (1)
- # leiningen (3)
- # nyc (1)
- # off-topic (6)
- # om (7)
- # onyx (6)
- # parinfer (11)
- # re-frame (23)
- # reagent (15)
- # ring-swagger (1)
- # rum (15)
- # shadow-cljs (37)
- # sql (24)
- # uncomplicate (4)
- # unrepl (17)
problem is there doesnt seem to be a timezone attached to the postgresql date type, just timestamp or time
If you have everything on UTC, you're fine. Or else everything on Eastern time. As soon as you have pieces on different timezones, you're sunk.
Like I say everything on UTC.
By default, the JVM will use the system timezone, but you can change it.
i see, i wonder why im seeing the same bug on my server…maybe cause im building the image in EST?
Server has a TZ. Database has a TZ. JVM has a TZ. 🙂
the server is UTC and I’m running the jar with the command java -Duser.timezone=UTC -jar service.jar
@jgh this is another option at startup of your app:
;; using java.util.TimeZone
(TimeZone/setDefault (TimeZone/getTimeZone "UTC"))