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.

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

migrate.py install_labels - Equivalent constraint already exists #58

Open
TACIXAT opened this issue Jul 1, 2021 · 0 comments
Open

migrate.py install_labels - Equivalent constraint already exists #58

TACIXAT opened this issue Jul 1, 2021 · 0 comments

Comments

@TACIXAT
Copy link

TACIXAT commented Jul 1, 2021

neo4j.exceptions.ClientError: {code: Neo.ClientError.Schema.EquivalentSchemaRuleAlreadyExists} {message: An equivalent constraint already exists, 'Constraint( id=2, name='constraint_bd9158e1', type='UNIQUENESS', schema=(:Device {uid}), ownedIndex=1 )'.}

Get this when rerunning install_labels. What is the correct workflow for partial migrations when adding a new node class? I can do clear_neo4j but that drops all nodes as well.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant