@lmergen the core idea is to give the option to users for being as specific as they want (i.e. writing migrations one at a time - complex or not) or allowing users to manage one schema and then letting Migrana deal with the migrations

awesome

i'm interested

cool… I’ll put a few lines together during the next weeks

Say, is there a version of :db.fn/retractEntity that doesn't recur into :db/isComponent true attributes?

Tangentially-related to the last question: let's say I have called retractEntity on entity 123 and I want to undo the transaction. Is it safe to add the data back as [:db.add 123 :attr value] seqs, or do I need to generate a new tempid and add the data in to the newly-created entity instead?

Thanks @favila!

Wired/Cool idea about @timgilbert problem

(d/function
  '{:lang :clojure :requires [[datomic.api :as d]] :params [db eid]
    :code (as-> '[:find ?add ?attr ?comp ?v
                  :in $ ?e
                  :where
                  [(ground :db/add) ?add]
                  [(ground :db/isComponent) ?comp]
                  [(ground false) ?v]
                  [?e ?i]
                  [?i :db/valueType :db.type/ref]
                  [?i :db/ident ?attr]] ↓
                (d/q ↓ db eid)
                (d/with db ↓)
                (:db-after ↓)
                (d/invoke db :db.fn/retractEntity ↓ eid))})