This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-09
Channels
- # admin-announcements (1)
- # boot (225)
- # braid-chat (1)
- # cider (25)
- # cljs-dev (35)
- # cljsrn (1)
- # clojars (6)
- # clojure (81)
- # clojure-berlin (1)
- # clojure-dev (21)
- # clojure-france (2)
- # clojure-japan (6)
- # clojure-poland (1)
- # clojure-russia (10)
- # clojure-uk (3)
- # clojurescript (121)
- # code-reviews (1)
- # core-async (4)
- # core-logic (2)
- # cursive (15)
- # datomic (8)
- # hoplon (4)
- # jaunt (112)
- # jobs-discuss (35)
- # om (41)
- # parinfer (8)
- # re-frame (3)
- # reagent (4)
- # ring (2)
- # untangled (38)
@randyt it's hard to tackle that question generically, but I think the basic point would be that yes, multi-table data can be migrated to Datomic usually and depending on e.g. how the tables are typically joined to answer questions, a Datomic schema may be a better fit, especially if it involves implied graphs, card many values, varying presence/absence of fields, etc.
I doubt there will be a generic ETL tool you can grab if the best fit for your data is a model fundamentally different in some ways than the relational/table model.
@bkamphaus: thanks for the feedback
If you know that you are transacting to only one entity, (only one map literal), what is the best way to get the entity id you transacted to from the transaction future. I was doing this via
(defn- get-e-id-for-transaction
[transaction-future]
((comp first vals :tempids)
@transaction-future))
But I realized that only works if you are transacting to a new entity since there won't be tempids in that case.http://docs.datomic.com/clojure/#C03RZMDSH.api/transact says :tx-data cotnains the datoms produced by a transaction, so maybe mapping first over that?