You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have two fields in a node with a similar name where the camel, and I use a projection when saving that refers one of them, the other will also get persisted. Take for example an entity class that looks like this:
publicclassPerson {
// ... class truncated for brevity ...@PropertyprivatebooleanfriendsAlsoEatDoritos;
@RelationshipprivateSet<Person> friends = newHashSet<>();
// ... class truncated for brevity ...
}
If I try to save an object of this class using this projection:
publicinterfacePropertiesProjection {
booleangetEatsDoritos();
// If you comment this out, tests will pass and the relationships won't get persisted:booleangetFriendsAlsoEatDoritos();
}
The objects in the friends set will also get persisted despite not being a part of the projection. Comment out the following line and the projection works as expected: boolean getFriendsAlsoEatDoritos(); (line 45 in the example's Person.java)
The text was updated successfully, but these errors were encountered:
Example project with a test that demonstrates the issue(
PersonNeo4jTest
):https://github.com/ejflick/sdn-projection-similar-name-issue
If I have two fields in a node with a similar name where the camel, and I use a projection when saving that refers one of them, the other will also get persisted. Take for example an entity class that looks like this:
If I try to save an object of this class using this projection:
The objects in the
friends
set will also get persisted despite not being a part of the projection. Comment out the following line and the projection works as expected:boolean getFriendsAlsoEatDoritos();
(line 45 in the example'sPerson.java
)The text was updated successfully, but these errors were encountered: