-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Neo.TransientError.Transaction.Outdated Error #12251
Comments
It occurs because your query is returning the deleted relationship, and the relationship object is not materialised (fully populated with properties, etc) until the result is being serialised, which, if you are using automatic rather than explicit transactions, happens after the transaction commits. |
@chrisvest thanks for the answer. Pardon my ignorance, but does it mean that you can return a deleted relationship? Is there a suggested alternative. The thing is that the same query works fine on version 3.3.3 but not in 3.5.8. |
If you need to return the properties of the relationship, you can project those out before your delete and return those:
If you want the graph ID of the relationship too (and anything else you might need) you can use map projection first before the deletion:
|
@chrisvest The error message |
@ppoliani The semantics of returning deleted entities are not well defined in the current Cypher versions. A proposal has been put forward that pins down the semantics in this area, but the current versions of Cypher do not yet implement it. Until then, we'll improve the error message. |
@chrisvest Thanks for the reference. Will @InverseFalcon solution work at the moment? |
@ppoliani Yes, capturing the properties with a |
Fantastic! Shall we remove the bug label and close this issue? |
I get an error from a query that used to run correctly.
Neo4j Version: 3.5.8-enterprice
Operating System: MacOS Mojave
API: Docker
Steps to reproduce
HAS_PERSONAL
relationshipExpected behavior
The relationship should be removed.
Actual behavior
I get the following error:
The text was updated successfully, but these errors were encountered: