| > I think the only case for which you should create a constraint instead of an index is when @Index(unique=true) is set to true. As I observed, when `unique=true` the index is automatically converted to unique constraint at higher level (not sure if it's by ORM). Thus, if a single column is requested, a regular constraint will be applied, otherwise ignored. > 13:29:52,832 WARN BaseNeo4jSchemaDefiner:187 - OGM001404: Neo4j does not support constraints spanning multiple columns. Unique key UK206nrc3pvx8net4xmspnd8520 for Neo4jIndexTest$Person on columns [firstname, nickname] cannot be created Non-unique indexes spanning multiple properties will be created normally after this fix. Should we also implement composite constraint as describe here in this issue scope? |
