-
Notifications
You must be signed in to change notification settings - Fork 617
Projection support for dynamic relationships #2533
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
Milestone
Comments
meistermeier
added a commit
that referenced
this issue
May 5, 2022
meistermeier
added a commit
that referenced
this issue
May 5, 2022
meistermeier
added a commit
that referenced
this issue
May 10, 2022
meistermeier
added a commit
that referenced
this issue
May 10, 2022
meistermeier
added a commit
that referenced
this issue
May 10, 2022
meistermeier
added a commit
that referenced
this issue
May 10, 2022
meistermeier
added a commit
that referenced
this issue
May 11, 2022
meistermeier
added a commit
that referenced
this issue
May 12, 2022
meistermeier
added a commit
that referenced
this issue
May 12, 2022
meistermeier
added a commit
that referenced
this issue
May 12, 2022
meistermeier
added a commit
that referenced
this issue
May 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using a dynamic relationship, the property filter does not get asked if it contains the property.
It does instantaneously continue to update all relationships.
This brings problems if an incomplete entity gets loaded and should get persisted with a projection "blueprint" via
Neo4jTemplate#saveAs
.Conversation: https://community.neo4j.com/t/how-to-correctly-update-a-relationship/55682
The text was updated successfully, but these errors were encountered: