hi all

I have this question

why does replacing embedded document (aka 'component' field of datascript) leaves orphaned internal entities?

(let [db (d/create-conn  {:heroku.app.id  {:db/unique :db.unique/identity}
                            :w             {:db/isComponent true
                                            :db/valueType :db.type/ref}})]
    (d/transact! db
                 [{:heroku.app.id 7 :w {:a 2 :b 3}}])
    (d/transact! db
                 [{:heroku.app.id 7 :w {:c 4 :d 5}}]))

database will have 3 entities instead of 2

(I have a guess that in datomic it would be more of a feature, though, to preserve history)

there’s no implicit delete

you have to retract your component explicitly

so will it be a good feature to cover this case (as a memory leak in upsert scenarios), or it can be considered more as a 'byproduct of design'?

can't say if I'd be able to provide pull request that soon though

also thank you for your reply

also - what does datomic do in this case? does it auto-retract embedded document?

(so that it won't appear in queries as an orphaned entity)

hm. I guess there are some use-cases for component entities to stay, I just can't figure out which. I remember different on-delete behavior for parents in ORMs for parent-children associations