are they two different values retracted? Is it a schema entity?

or, do you have the log?

this is from the log. the two retractions have equal values, and are different from the assertion

ah, so if you explicitly retract and assert a new value on the same e and card-1 attr, datomic may not drop the redundant retraction. This is an issue we encountered during decanting (it made decanting an already-decanted database break). I don’t remember if this was fixed

what is decanting?

ahhh... ok, and in this case we certainly would be doing that

that was my other question :D

decanting is replaying and transforming the tx log on one db to fill a new db