ASSERT_INDEX does not work more than once in GoGM 2.2.0
SaraBroad opened this issue · 1 comments
ASSERT_INDEX does not work more than once in the newest version of GoGM. https://community.neo4j.com/t/why-does-creating-a-duplicate-constraint-error-out-in-4-x-but-not-in-3-x/17967
It appears the new version of GoGM did not take into account some of the changes in the neo4j 4.x driver.
We are seeing failed to init gogm instance, failed managed write tx, failed to execute query, Neo4jError: Neo.ClientError.Schema.EquivalentSchemaRuleAlreadyExists (An equivalent constraint already exists...
ASSERT_INDEX works when we revert back to version 2.0.2.
@SaraBroad thanks for reporting this issue. I just pushed a patch that should resolve this. Please reopen this issue if the problem persists. Pull version v2.2.1