Neo4j constraints should be used for primary key (maybe composite) and are required for ash identities.
https://neo4j.com/docs/cypher-manual/current/constraints/managing-constraints/
These should be optional as if used increase developer overhead as ash.codegen and ash.neo4j.migrate etc would need to be used to generate and execute neo4j schema.
We'd limit this to features available in the community edition, which means we can't enforce uniqueness across combinations of properties and labels.
Minimum would be to enforce uniqueness on a primary key attribute on a resource. This doesn't make the property globally unique.
Neo4j constraints should be used for primary key (maybe composite) and are required for ash identities.
https://neo4j.com/docs/cypher-manual/current/constraints/managing-constraints/
These should be optional as if used increase developer overhead as ash.codegen and ash.neo4j.migrate etc would need to be used to generate and execute neo4j schema.
We'd limit this to features available in the community edition, which means we can't enforce uniqueness across combinations of properties and labels.
Minimum would be to enforce uniqueness on a primary key attribute on a resource. This doesn't make the property globally unique.