Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ASSERT_INDEX does not work more than once in GoGM 2.2.0 #73

Closed
SaraBroad opened this issue Oct 11, 2021 · 1 comment
Closed

ASSERT_INDEX does not work more than once in GoGM 2.2.0 #73

SaraBroad opened this issue Oct 11, 2021 · 1 comment

Comments

@SaraBroad
Copy link

SaraBroad commented Oct 11, 2021 •
edited
Loading

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.
@erictg
Copy link
Member

erictg commented Oct 22, 2021 •
edited
Loading

@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

@erictg erictg closed this as completed Oct 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@erictg @SaraBroad