datomic

Ask questions on the official Q&A site at https://ask.datomic.com!
onetom 2021-06-10T06:22:10.180600Z

i was also fighting with those conflicts lately. luckily, you don't HAVE TO necessarily fix all of them, but obviously that's an unsupported situation. in my case, the main conflict was caused by the jackson lib and it actually prevented my program to start, even locally. after applying these adjustments: https://github.com/metosin/muuntaja/issues/121 and ignoring some of the remaining conflicts, things seem to work. so far...

onetom 2021-06-10T06:52:24.182500Z

is it possible to undivert a datomic system, which has been diverted by datomic.dev-local/divert-system, or should i restart my repl, if i want to do another datomic.dev-local/import-cloud for example?

onetom 2021-06-10T06:58:42.184100Z

im also getting an error like this:

Execution error (IllegalArgumentException) at datomic.dev-local.impl/fn (impl.clj:490).
This client does not support dev-local import.
from import-cloud:
(dl/import-cloud
    {:source {:server-type :ion,
              :region      "ap-southeast-1",
              :system      "XXX",
              :endpoint    "<http://entry.XXX.ap-southeast-1.datomic.net:8182/>",
              :proxy-port  8182,
              :db-name     "DBDBDB"}
     :dest   {:server-type :dev-local
              :storage-dir :mem
              :system      "tmp"
              :db-name     "copy1"}
     :filter {}})
i've tried both com.datomic/client-cloud v`0.8.102` and v`0.8.105`; same error.

onetom 2021-06-10T07:20:22.184400Z

ah, it seems, i can't import into an in-memory dev-local system 😞 if i use (str (io/file (System/getProperty "user.home") ".datomic" "local")) instead of :mem, then the import succeeds.

onetom 2021-06-10T07:34:14.188700Z

is there any reason for not supporting "dev-local import" into in-memory systems?

onetom 2021-06-10T07:20:22.184400Z

ah, it seems, i can't import into an in-memory dev-local system 😞 if i use (str (io/file (System/getProperty "user.home") ".datomic" "local")) instead of :mem, then the import succeeds.

onetom 2021-06-10T07:32:02.188600Z

in the https://docs.datomic.com/cloud/dev-local.html#import-cloud example, the source and the destination datomic :system names and :db-names are different. do i understand well, that if i want to use dl/divert-system, then my imported copy should have the same :system and :db-name? it feels very error-prone, because if i forget to call diver-system, i might end up modifying the cloud db, instead of the local copy and im not sure how would i even notice the mistake. are there any videos / articles demonstrating this workflow?

onetom 2021-06-10T07:34:14.188700Z

is there any reason for not supporting "dev-local import" into in-memory systems?

favila 2021-06-10T22:02:23.190300Z

I filed a support ticket for this.

favila 2021-06-10T22:02:38.190600Z

#3163

2021-06-10T22:03:17.191100Z

I'm curious if there was some thought in the past about adding a query planner to datomic (where the user-specified clause ordering is not meaningful), and if so why it was decided against - and if it hasn't, would there be consideration of adding it?