This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-19
Channels
- # announcements (9)
- # babashka (11)
- # beginners (157)
- # calva (10)
- # cider (18)
- # clara (4)
- # clj-kondo (40)
- # cljsrn (8)
- # clojure (29)
- # clojure-europe (11)
- # clojure-italy (1)
- # clojure-nl (2)
- # clojure-spec (4)
- # clojure-sweden (1)
- # clojure-uk (39)
- # clojurescript (32)
- # conjure (1)
- # core-async (2)
- # cursive (20)
- # datomic (7)
- # duct (9)
- # emacs (1)
- # figwheel-main (1)
- # fulcro (24)
- # helix (1)
- # hoplon (20)
- # hugsql (3)
- # jackdaw (5)
- # jobs-discuss (7)
- # lambdaisland (1)
- # malli (5)
- # music (4)
- # off-topic (54)
- # parinfer (2)
- # pedestal (13)
- # re-frame (12)
- # reagent (22)
- # reitit (9)
- # shadow-cljs (89)
- # spacemacs (2)
- # xtdb (21)
AFAIK there's no :duct/database
key, there is a :duct.database/sql
though. For example the hikaricp duct init key derived from this. That way you can reference it as :duct.database/sql
. If you switch to a different database pool you won't have to change this key
Thanks, @kevin.van.rooijen, but I found it in another lib being used.
Looks like I was mistaken. It's in the code base I'm working, passed with :duct/daemon
to the top-level ig/init
. Not the best name for that key 😕
Ah ok, so they're starting whatever derives from :duct/database on boot I guess. A bit strange unless no other keys are referring to that key