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

GH-746 - Fix optimistic locking for relationship entities. #747

Merged
merged 2 commits into from
Jan 22, 2020

Conversation

meistermeier
Copy link
Collaborator

@meistermeier meistermeier commented Jan 21, 2020

Reset the version attribute on a virtually new relationship entity if the target node has changed.
The solution is pretty much straight-forward but there is no better place to not affect other parts of the mapping to track a "new" relationship entity.

Closes #746

Also reset the version attribute on a virtually new relationship entity
if the target node has changed.
Copy link
Collaborator

@michael-simons michael-simons left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great find and sorry for messing up your day with that.

Co-Authored-By: Michael Simons <michael.simons@neo4j.com>
@meistermeier meistermeier merged commit a50b657 into master Jan 22, 2020
meistermeier added a commit that referenced this pull request Jan 22, 2020
Also reset the version attribute on a virtually new relationship entity
if the target node has changed.

(cherry picked from commit a50b657)
@michael-simons michael-simons deleted the issue/GH-746 branch January 22, 2020 07:59
meistermeier added a commit that referenced this pull request Jan 22, 2020
Also reset the version attribute on a virtually new relationship entity
if the target node has changed.

(cherry picked from commit a50b657)
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

Successfully merging this pull request may close these issues.

OptimisticLockingException when updating a RelationshipEntity object
2 participants