This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-30
Channels
- # announcements (2)
- # babashka (3)
- # beginners (31)
- # biff (3)
- # calva (40)
- # chlorine-clover (2)
- # clerk (5)
- # clj-kondo (10)
- # clojure (13)
- # clojure-art (1)
- # clojure-denver (16)
- # clojure-europe (44)
- # clojure-nl (1)
- # clojure-norway (27)
- # clojure-sweden (3)
- # clojure-uk (1)
- # clojurescript (49)
- # clr (6)
- # community-development (2)
- # datalevin (10)
- # datomic (63)
- # events (2)
- # fulcro (9)
- # holy-lambda (15)
- # honeysql (8)
- # hoplon (6)
- # hyperfiddle (9)
- # introduce-yourself (1)
- # kaocha (1)
- # london-clojurians (2)
- # matrix (1)
- # nbb (7)
- # off-topic (38)
- # polylith (6)
- # re-frame (4)
- # reagent (2)
- # releases (3)
- # sci (13)
- # scittle (5)
- # shadow-cljs (6)
- # sql (5)
- # tools-deps (4)
- # vim (33)
- # web-security (8)
- # xtdb (2)
Hi, why does honeysql formats at?
with two question marks?
(hsql/format [pg-ops/at? [:-> :a :b] "something"] {:inline true})
=> ["(a -> b) @?? 'something'"]
That seems like an escape sequence. A single ?
is a parameter, and ??
is a literal ?
, perhaps.
DBeaver considers it as an input parameter with one and two question marks. If the interpretation of ? as an input parameter is turned off, both versions work the same.
Yeah, I wouldn't compare a string designed to be prepared with JDBC to something that DBeaver expects. There can be all sorts of potential differences.
If that @??
works just fine, then all is well. If it doesn't, then it should be an issue for HoneySQL.
@U2FRKM4TW Sure, but it would be nice to have it there )).
The goal of HoneySQL is primarily to produce a vector of SQL + params for use with clojure.java.jdbc
or next.jdbc
. If you use its output for something else, you may well need to make some adjustments.