This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-29
Channels
- # admin-announcements (2)
- # beginners (10)
- # boot (253)
- # cider (11)
- # cljs-dev (26)
- # cljsjs (21)
- # cljsrn (7)
- # clojure (87)
- # clojure-berlin (13)
- # clojure-dusseldorf (5)
- # clojure-greece (7)
- # clojure-poland (11)
- # clojure-russia (189)
- # clojure-spec (31)
- # clojure-uk (86)
- # clojurescript (89)
- # cursive (15)
- # datavis (2)
- # datomic (57)
- # devcards (3)
- # dirac (92)
- # editors-rus (3)
- # emacs (4)
- # events (1)
- # funcool (30)
- # hoplon (3)
- # jobs-rus (6)
- # leiningen (1)
- # luminus (12)
- # mount (25)
- # off-topic (5)
- # om (43)
- # onyx (41)
- # perun (1)
- # proton (2)
- # protorepl (7)
- # re-frame (17)
- # reagent (34)
- # ring (13)
- # specter (1)
- # spirituality-ethics (1)
Re luminus and feedback loops: I’d agree with @yogthos. Given that Luminus is not a traditional framework, even if it became the de facto starting point, nothing stops people from trying out other things.
Postgres driver 9.4.1209 doesn’t contain a JDBC4Array. Neither does 9.4.1209.jre7. Can’t quite find when that was removed, or if it was split to a different library. Any ideas?
Last version I can find that explicitly refers to jdbc4 is the 9.4-1206-jdbc41 which Luminus currently references.
yeah that’s actually the reason I haven’t upgraded yet either, haven’t had a chance to see what happened there
@yogthos @ricardo : Here's the relevant issue stating that the JDBC4Array class is an internal API with the alternative being 'java.sql.Array
: https://github.com/pgjdbc/pgjdbc/issues/559
So sounds like just have to refactor how arrays are handled in the luminus template then
I guess so. 😞
Thanks @curtis.summers And speaking of which, thanks for HugSQL too. 🙂