[jira] [Commented] (CAY-1860) In-memory matching of DataObjects against ObjectId or int

["Andrus Adamchik (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAY-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727686#comment-13727686 ] 

Andrus Adamchik commented on CAY-1860:
--------------------------------------

Subtle differences in in-memory matching will result from this change. Aside from being able to match objects with numbers, now objects in 2 ObjectContexts are compared purely by ObjectId. Their persistent state of property sets are completely ignored now. I.e. prior to 3.2M2 o1 and o2 having matching ObjectId, sitting in c1 and c2 , but having different local modifications would not match each other when compared in-memory. Now they will match.
                
> In-memory matching of DataObjects against ObjectId or int
> ---------------------------------------------------------
>
>                 Key: CAY-1860
>                 URL: https://issues.apache.org/jira/browse/CAY-1860
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: Core Library
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>             Fix For: 3.2M2
>
>
> This is to bring in-memory expression eval closer to the its DB equivalent. Consider the expression:
>  "artist = $a"
> 1. if "a" is a DataObject, this works the same in-memory and when executed against the DB as a part of SelectQuery qualifier.
> 2. if "a" is ObjectId this works as a part of the query, but doesn't work in-memory
> 3. If "a" is a Number this works as a part of the query, but doesn't work in-memory
> So we need to fix cases 2 & 3.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira