Fork me on GitHub
#datomic
<
2019-11-24
>
favila04:11:00

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.

ackerleytng23:11:31

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?

bhurlow00:11:54

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

bhurlow00:11:50

actually just seeing the mem flag here, with mem transactor is built in to the library, other protocols dev,`ddb` etc behave as above