This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-21
Channels
- # announcements (4)
- # aws (29)
- # aws-lambda (1)
- # babashka (21)
- # beginners (143)
- # calva (47)
- # cider (31)
- # clj-kondo (24)
- # cljsrn (4)
- # clojure (70)
- # clojure-australia (3)
- # clojure-czech (1)
- # clojure-europe (97)
- # clojure-greece (4)
- # clojure-nl (3)
- # clojure-uk (45)
- # clojurescript (70)
- # code-reviews (1)
- # conjure (7)
- # cursive (10)
- # datomic (13)
- # duct (5)
- # emacs (1)
- # fulcro (38)
- # graalvm (1)
- # graphql (9)
- # honeysql (13)
- # integrant (33)
- # jobs (14)
- # jobs-rus (1)
- # malli (7)
- # off-topic (72)
- # pathom (1)
- # re-frame (11)
- # reitit (9)
- # remote-jobs (2)
- # sci (11)
- # shadow-cljs (9)
- # sql (5)
- # tools-deps (5)
- # xtdb (6)
@kaxaw75836 are you using the helper functions or just the raw data structure?
In general with HoneySQL, if :foo
is a SQL entity then [:foo :bar]
is a SQL entity with an alias.
I prefer the helpers. I wish more people used them.
It's really hard to get the raw data structures right. The helpers... well... help.
Just dynamic ones. We don't use HoneySQL for static queries. And we only use the helpers, not the raw data structure. And we're heavy users of HoneySQL -- one of my colleagues did a Clojure/West talk about it in 2015 (I think).
fwiw, I code honey using the data structures directly. the only real problem is that, when i get something wrong, the resulting error message isn't terribly helpful but i can generally visually spot the problem in a minute or two of examining the data structure. i'm looking forward to honey 2.0 and spec. not only do i expect the error messages to get better, i think spec will make it easier to programmaticly manipulate queries.