<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Datomic Knowledgebase - Recent questions tagged :db.cardinality one</title>
<link>https://ask.datomic.com/index.php/tag/%3Adb.cardinality+one</link>
<description>Powered by Question2Answer</description>
<item>
<title>Why is :db.unique/identity only allowed on :db.cardinality/one?</title>
<link>https://ask.datomic.com/index.php/690/why-is-db-unique-identity-only-allowed-on-db-cardinality-one</link>
<description>&lt;p&gt;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.&lt;/p&gt;
</description>
<category>On-Prem</category>
<guid isPermaLink="true">https://ask.datomic.com/index.php/690/why-is-db-unique-identity-only-allowed-on-db-cardinality-one</guid>
<pubDate>Tue, 21 Dec 2021 18:21:49 +0000</pubDate>
</item>
</channel>
</rss>