This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-27
Channels
- # aleph (1)
- # announcements (5)
- # babashka (13)
- # beginners (68)
- # brompton (7)
- # calva (10)
- # cider (1)
- # clara (15)
- # cljsrn (2)
- # clojure (63)
- # clojure-austin (1)
- # clojure-europe (44)
- # clojure-france (2)
- # clojure-nl (5)
- # clojure-norway (1)
- # clojure-poland (1)
- # clojure-uk (8)
- # clojurescript (8)
- # clojureverse-ops (7)
- # conjure (13)
- # core-async (27)
- # cryogen (10)
- # cursive (17)
- # datomic (13)
- # deps-new (1)
- # events (1)
- # fulcro (3)
- # gratitude (4)
- # helix (6)
- # honeysql (6)
- # introduce-yourself (1)
- # jobs (2)
- # malli (13)
- # meander (9)
- # music (1)
- # news-and-articles (2)
- # off-topic (8)
- # pedestal (1)
- # reitit (4)
- # sci (25)
- # shadow-cljs (13)
- # spacemacs (2)
- # tools-build (5)
- # tools-deps (20)
- # vscode (50)
- # xtdb (2)
I’m just curious, I was doing some refactoring and “create-architect2” throws a HStore extension not installed. I did some initial digging and it appears to be json related which means ‘[:lift …]’ is throwing it off. My first ‘create-architect’ function works fine, but I’d like to know what’s so different in the background here?
@decim were you passing the lifted value into the working version?
@seancorfield yup, same exact way, I literally just copied the function call over and changed the name and wrapped it in (query! …)
I'm not at my computer so I can't try anything but I don't see anything obvious on my phone
@seancorfield hmm, ok. It’s a bit odd. The initial function works but clearly something is thrown off. I’ll continue to toy with it a little later tonight.
@decim I ran both of these and they produce identical results -- in terms of what is handed off to next.jdbc
so I don't think this is a HoneySQL issue (nor a bug in your code). Something else must be at play here.