You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2014/08/29 16:50:54 UTC

[jira] [Created] (CAY-1947) Extraneous UPDATE on phantom toOne

Andrus Adamchik created CAY-1947:
------------------------------------

             Summary: Extraneous UPDATE on phantom toOne
                 Key: CAY-1947
                 URL: https://issues.apache.org/jira/browse/CAY-1947
             Project: Cayenne
          Issue Type: Bug
    Affects Versions: 3.2M1
            Reporter: Andrus Adamchik
            Assignee: Andrus Adamchik
            Priority: Minor


in a 1..N relationship, where there's no corresponding N..1 on the object side, a phantom update (same to-one set twice) causes an UPDATE query that is essentially a noop. See https://github.com/nhl/link-rest/issues/28. This comes down to the fact that we do not analyze "phantomFks" inside ObjectDiff.isNoop(..). (Or maybe when we resolve to-many and find phantom objects are already in it, we should unregister a change from ObjectStore?)



--
This message was sent by Atlassian JIRA
(v6.2#6252)