This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-14
Channels
- # beginners (116)
- # boot (6)
- # cider (16)
- # cljdoc (5)
- # cljsrn (3)
- # clojure (156)
- # clojure-conj (5)
- # clojure-finland (1)
- # clojure-italy (46)
- # clojure-mexico (36)
- # clojure-russia (2)
- # clojure-sanfrancisco (1)
- # clojure-spec (10)
- # clojure-uk (69)
- # clojurescript (71)
- # core-async (2)
- # cursive (18)
- # datomic (91)
- # duct (2)
- # editors (1)
- # emacs (5)
- # figwheel-main (11)
- # fulcro (31)
- # graphql (8)
- # hispano (1)
- # jobs (1)
- # jobs-discuss (2)
- # lambdaisland (1)
- # london-clojurians (1)
- # nyc (1)
- # off-topic (104)
- # onyx (34)
- # parinfer (3)
- # pedestal (2)
- # precept (17)
- # protorepl (2)
- # re-frame (13)
- # reagent (4)
- # ring-swagger (52)
- # shadow-cljs (92)
- # spacemacs (17)
- # sql (14)
- # tools-deps (6)
- # unrepl (4)
- # vim (39)
@djtango it is tested against whatever version is in the project's deps.edn
file but should work with any recent version.
(I'm not at my desk right now to look up what version that is)
@djtango if you use a connection pooling library, then you'll probably want to check it's recommendations for setting it up with postgres, the postgres JDBC driver has had a number of improvements in the last 3 years that require less specific changes to work optimally in pools (namely, I believe the support for jdbc4's connection checking was added, which means you don't need to set a default query to check the connection status anymore)
could be wrong about that...but that's what my overly faulty memory is thinking, so can't hurt to check it out
the hikariCP author had a change in the postgres driver that got merged last year ( https://github.com/pgjdbc/pgjdbc/pull/849 ) , but you'll benefit from that without having to do any configuration changes