constraint issue (create before delete) with mergeNodes #303
Comments
|
We could backup the information into a VirtualNode + List, delete the source and copy from Virtual to target. |
|
it should also work if we pull out the properties as a map
Then transfer rels
Delete node
And only then set properties
Von meinem iPhone gesendet
… Am 07.04.2017 um 19:41 schrieb Lorenzo Speranzoni ***@***.***>:
We could backup the information into a VirtualNode + List, delete the source and copy from Virtual to target.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
DanielBerton
pushed a commit
to AngeloBusato/neo4j-apoc-procedures
that referenced
this issue
Apr 14, 2017
DanielBerton
pushed a commit
to AngeloBusato/neo4j-apoc-procedures
that referenced
this issue
Apr 14, 2017
DanielBerton
pushed a commit
to AngeloBusato/neo4j-apoc-procedures
that referenced
this issue
Apr 14, 2017
DanielBerton
pushed a commit
to AngeloBusato/neo4j-apoc-procedures
that referenced
this issue
Apr 19, 2017
albertodelazzari
pushed a commit
to albertodelazzari/neo4j-apoc-procedures
that referenced
this issue
Jun 28, 2017
ncordon
pushed a commit
to ncordon/neo4j-apoc-procedures
that referenced
this issue
Nov 1, 2023
…j-contrib#303) * [ROQ0fkdz] Reduce the number of transactions we use in triggers * [ROQ0fkdz] Open new transaction only when needed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failed to invoke procedure
apoc.refactor.mergeNodes: Caused by: org.neo4j.graphdb.ConstraintViolationException: Node 1250 already exists with label Organization and property "name"=[INVESCO, LTD.]we need to delete the node first (or at least the key property) before creating a new one
The text was updated successfully, but these errors were encountered: