This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-09
Channels
- # announcements (16)
- # beginners (86)
- # calva (4)
- # cider (17)
- # circleci (1)
- # clj-kondo (4)
- # cljs-dev (12)
- # cljsrn (4)
- # clojure (82)
- # clojure-europe (2)
- # clojure-houston (4)
- # clojure-italy (5)
- # clojure-nl (7)
- # clojure-spec (49)
- # clojure-uk (19)
- # clojurescript (76)
- # core-async (7)
- # cursive (1)
- # data-science (4)
- # datomic (5)
- # figwheel (1)
- # fulcro (10)
- # graalvm (15)
- # jobs (1)
- # juxt (6)
- # kaocha (2)
- # leiningen (5)
- # random (2)
- # shadow-cljs (25)
- # sql (5)
- # tools-deps (113)
- # vim (3)
- # yada (14)
Fixed in next.jdbc
on master.
(although it's more important in the Clojure identifier -> SQL entity direction -- since that will break SQL -- whereas in the other direction, Turkish users would still get valid Clojure keywords... they'd just perhaps not be what they expected)
@seancorfield thanks! i see it's fixed in java.jdbc too 🙂
Yeah, just pushed a fix for that as well.
Not sure when 0.7.10 will get released (`java.jdbc`), nor 1.0.6 (`next.jdbc`), but you can use them via deps.edn
on master for now.