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
When merging an instance with a reference to another instance, JOPA calculates changes on the reference and considers it a change if any of its attributes have changed, even though it should only check that it is the same instance. An example:
A.hasB = B;
B.name = "Test";
persist(A, B);
B.name = null;
result = merge(A)
=> hasChanges(A) == true, which is wrong, because B is still the same instance.
Correct behavior:
hasChanges(A) == false && result.hasB.name == "Test", because there is no cascading to B, so the value from storage should be used.
The text was updated successfully, but these errors were encountered:
When merging an instance with a reference to another instance, JOPA calculates changes on the reference and considers it a change if any of its attributes have changed, even though it should only check that it is the same instance. An example:
A.hasB = B;
B.name = "Test";
persist(A, B);
B.name = null;
result = merge(A)
=> hasChanges(A) == true, which is wrong, because B is still the same instance.
Correct behavior:
hasChanges(A) == false && result.hasB.name == "Test", because there is no cascading to B, so the value from storage should be used.
The text was updated successfully, but these errors were encountered: