Unique and key constraints blocks certain valid writes

[james-whiteside]

Description

When inserting two ownerships of the same unique or key attribute by the same owner, TypeDB throws an error. This should not be the case as attribute idempotency will ensure that the data that is actually written does not violate the constraint.

Environment

1. TypeDB distribution: Core
2. TypeDB version: ef289da
3. Environment: MacOS
4. Client and version: Studio b44218f

Reproducible Steps

1. Run:

define
person sub entity;
person owns id @key;
person owns email @unique;
person owns name;
id sub attribute, value string;
email sub attribute, value string;
name sub attribute, value string;

2. Run:

insert
$p3 isa person, has id "p3", has id "p3", has email "p3", has email "p3";

Expected result

TypeDB identifies that data write query will not violate @unique constraint on email, or the @key constraint on id.