Welcome! Please see the About page for a little more info on how this works.

0 votes
in On-Prem by

I'm curious about the rationale for only allowing :db.cardinality/one attributes to be :db.unique/identity? An immediate use case in the wild is email addresses, which uniquely identify an individual but an individual can have many email addresses.

1 Answer

0 votes

I decided to not trust the documentation and, as of version 0.9.5697 of datomic-free, :db.cardinality/many attributes can be :db.unique/identity, in disagreement with:


Uniqueness can be declared on attributes of any value type, including
references (:db.type/ref). Only (:db.cardinality/one) attributes can
be unique.

In testing I found that the schema of a :db.cardinality/many :db.unique/identity attribute was accepted and that entity upsert worked fine across multiple instances of the attribute (i.e. the right behavior).

How can we get the documentation updated?

Welcome to the Datomic Knowledgebase, where you can make features requests, ask questions and receive answers from other members of the community.