Fork me on GitHub
#datomic
<
2018-05-07
>
dominicm11:05:49

I'm pretty sure I recall that it is not supported

octahedrion11:05:16

so confusing - where's the documentation ? There's nothing here https://docs.datomic.com/on-prem/moving-to-cloud.html to suggest it doesn't support multiple dbs (maybe there is, but not to my naive eye)

octahedrion11:05:21

ok I think I've found it: https://docs.datomic.com/on-prem/clients-and-peers.html "cross database joins" is "no" in the client column

octahedrion11:05:56

that, combined with https://docs.datomic.com/on-prem/moving-to-cloud.html#sec-3 "Apps that make heavy use of peer locality will require substantial alteration for Cloud"

octahedrion11:05:43

does suggest Datomic Cloud doesn't support multiple database queries, which is a shame since it's an appealing feature

octahedrion11:05:04

I wish Datomic's documentation was much clearer for newbies

robert-stuttaford11:05:04

@octo221 Cloud is still brand new. although they don’t say it anywhere, you can basically treat Cloud as “Beta”.

octahedrion12:05:18

does Datomic cloud support in-memory dbs ?

Alex Miller (Clojure team)12:05:53

No - the data is ... in the cloud

octahedrion12:05:26

the cloud is just other computers though

octahedrion12:05:15

i mean in-memory on the other computers - not the client

Alex Miller (Clojure team)15:05:49

data is cached across many levels in Datomic cloud, possibly including memory. but you generally shouldn’t know or care.

favila16:05:41

@octo221 I think the answer is no, datomic cloud does not give you any storage choices, so mem-only db is not possible

octahedrion17:05:32

@alexmiller @favila ok thanks for the clarification. I guess it's ok to create disposable dbs for testing and then delete them afterwards

Alex Miller (Clojure team)18:05:40

yes, that’s the approach I’ve used - in a fixture, create a database whose name includes a uuid, test, then delete