With the changes in #1548 and #1560 , we deleted the reverse has_one rel if we found there already exists one before creating a new one. We are correcting this with adding a config flag enforce_has_one, which when set will raise a error rather than deleting relations silently. Flag is by default not set and the has_one rel restriction is not enforced.
Additional information which could be helpful if relevant to your issue:
With the changes in #1548 and #1560 , we deleted the reverse has_one rel if we found there already exists one before creating a new one. We are correcting this with adding a config flag
enforce_has_one, which when set will raise a error rather than deleting relations silently. Flag is by default not set and the has_one rel restriction is not enforced.Additional information which could be helpful if relevant to your issue:
Code example (inline, gist, or repo)
Runtime information:
Neo4j database version:
neo4jgem version: 9.5.2neo4j-coregem version: NA