This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-02
Channels
- # beginners (7)
- # calva (10)
- # cider (9)
- # cljdoc (2)
- # cljsrn (10)
- # clojure (35)
- # clojure-europe (1)
- # clojure-greece (1)
- # clojure-spec (31)
- # clojure-uk (6)
- # clojurescript (3)
- # community-development (2)
- # cursive (37)
- # duct (5)
- # emacs (7)
- # fulcro (40)
- # hoplon (7)
- # off-topic (8)
- # parinfer (1)
- # quil (6)
- # re-frame (7)
- # reagent (7)
- # shadow-cljs (45)
- # sql (17)
- # tools-deps (12)
- # yada (3)
Thanks @seancorfield, appreciate it.
^ @amarjeet Already fixed on master BTW 🙂
(0.7.10 will be a while but if you're using clj
/`deps.edn` you can rely on git for it, or else git clone and mvn install)
I think, in addition to numbers, other data types will also have :default value issue, ex- boolean
Just CCing @seancorfield - whenever you get time to check. Thanks
SQL does not have Booleans. For BIT
it has b'0'
and b'1'
.
clojure.java.jdbc
does no translation of Clojure values to SQL values-in-strings.
One of the things that means (and it's true for HoneySQL and other SQL/JDBC libs), is that "foo"
is a Clojure string but not necessarily a SQL string. You need to say "'foo'"
.
That's why these libs assume PreparedStatement
s and ?
placeholders where you pass Clojure values and let the JDBC driver do the conversion.
This is another reason why DDL is so problematic. In SQL, you can pretty much do anything with PreparedStatement
s and ?
placeholders.