How to deprecate a composite tuple?

Question

As Datomic does not allow deleting attributes from schema we use the policy of adding a prefix to the attributes that are no longer used, e.g. :foo/bar becomes :foo/#bar. We then stop inserting deprecated attributes in the app code. This way old entities get to keep deprecated attributes, new ones do not have them. This works with all kinds of attributes, however this is not sufficient for composite tuples as Datomic calculates/inserts their values automatically.

Is there a way to instruct Datomic to stop populating a composite tuple?

Answer 1

Hi! You cannot currently stop populating a composite tuple. You can stop using it, but so long as you are updating the constitute attributes Datomic will continue to maintain and populate the tuple.

Answer 2

I had the same problem, actually it was problem when an old composite tuple attribute was marked as unique so the solution was to retract unique constraint