You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon further reflection, it's pretty weird to have an attribute that is both a :db.type/ref and :db.unique/identity. We changed our schema to {:db/unique :db.unique/value}, and the transactions with tempids are working.
I'll leave this issue open in case there might be a reason to have a ref with unique identity in someone's schema.
When transacting data that contains an attribute that is both
:db.unique/identity
and:db.type/ref
, it appears tempids don't work.Example:
This fails with:
The text was updated successfully, but these errors were encountered: