This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-24
Channels
- # announcements (11)
- # beginners (72)
- # calva (11)
- # cider (12)
- # clj-kondo (147)
- # clojure (6)
- # clojure-new-zealand (2)
- # clojuredesign-podcast (2)
- # clojurescript (36)
- # cursive (2)
- # datomic (5)
- # emacs (4)
- # fulcro (57)
- # graalvm (104)
- # graphql (2)
- # jobs (1)
- # joker (1)
- # kaocha (3)
- # malli (51)
- # off-topic (2)
- # portkey (1)
- # reagent (18)
- # shadow-cljs (26)
- # spacemacs (7)
- # tools-deps (5)
- # vim (4)
I’m using datomic analytics and want a :joins
through two “levels” of refs. Is this supported/supportable? example: metaschema {:tables {:foo/id {} :bar/x {}} :joins {:foo/bar-card1-ref "bar" :bar/card1-enum-ref "db__idents"}}
I expect/hope-for a foo.bar_card1_ref__card1_enum_ref__ident
column, but there is none.
When I run bin/run -m datomic.peer-server -h localhost -p 8998 -a myaccesskey,mysecret -d hello,datomic:
, is a transactor started somewhere in the background?
no, transactor must run as separate process (assuming on-prem). When transactor starts it stores it’s addressable location in the backend storage. When peer starts it finds that stored location and can then contact transactor directly
actually just seeing the mem
flag here, with mem
transactor is built in to the library, other protocols dev
,`ddb` etc behave as above
i see, thanks @U0FHWANJK!