This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-03
Channels
- # announcements (35)
- # aws (20)
- # babashka (4)
- # beginners (88)
- # cider (9)
- # clara (1)
- # clj-kondo (6)
- # cljsrn (3)
- # clojure (107)
- # clojure-dev (7)
- # clojure-europe (99)
- # clojure-nl (3)
- # clojure-spec (9)
- # clojure-uk (2)
- # clojurescript (28)
- # core-async (53)
- # cursive (11)
- # datascript (1)
- # datomic (2)
- # emacs (20)
- # fulcro (3)
- # graalvm (4)
- # holy-lambda (18)
- # jobs (1)
- # kaocha (7)
- # leiningen (2)
- # lsp (25)
- # luminus (1)
- # membrane-term (52)
- # missionary (8)
- # nextjournal (19)
- # off-topic (16)
- # other-languages (3)
- # podcasts-discuss (2)
- # polylith (23)
- # re-frame (4)
- # reclojure (6)
- # remote-jobs (1)
- # rewrite-clj (36)
- # ring (1)
- # sci (10)
- # shadow-cljs (7)
- # spacemacs (5)
- # sql (20)
- # uncomplicate (1)
- # vscode (3)
- # xtdb (27)
Hi! I am in need of providing my own :qualifier-fn and :label-fn opts to next.jdbc but I would need to know of the result of qualifier-fn when label-fn is called. It seems to me that's not possible with the current API, but maybe I'm doing things wrong?
@pyr Can you explain what problem you are trying to solve?
which allows you for instance to say (query :my.entities.account [:my.entities.account/name])
but in the odd case, the conversion that csk does might not map to the actual column name in the underlying seql schema
OK, so probably best plan of attack is to write your own variant of next.jdbc.result-set/get-modified-column-names
and then your own version of next.jdbc.result-set/as-modified-maps
and use that as your builder. It's only a few lines of code (and you could even do it in one function).
I would advise using your own option key if you need one, rather than confusing people by reusing qualifier-fn/label-fn but with different meanings.
It sounds like you need a builder that is specific to seql anyway?