[ https://issues.apache.org/jira/browse/CAY-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910572#comment-13910572 ]
Andrus Adamchik edited comment on CAY-1902 at 2/24/14 5:51 PM: --------------------------------------------------------------- [~johnthuss] Yeah, I guess if we have a multi-step path, fetch is unavoidable. But wonder if we can avoid a cast to DataContext and a call to objectStore.getCachedSnapshot(oid) (this can return null - the underlying cache is an LRU after all, and can overflow and lose some snapshots). For multi-step paths, I would probably just reverse the entire path (by going through each component and doing DbRelationship.createReverseRelationship(..)) and build a single query. was (Author: andrus): [~johnthuss] Yeah, I guess if we have a multi-step path, fetch is unavoidable. But wonder if we can avoid a cast to DataContext, a call to objectStore.getCachedSnapshot(oid) (this can return null - the underlying cache is an LRU after all, and can overflow and lose some snapshots). For multi-step paths, I would probably just reverse the entire path (by going through each component and doing DbRelationship.createReverseRelationship(..)) and build a single query. > Implement resolving Db paths for DataObjects > -------------------------------------------- > > Key: CAY-1902 > URL: https://issues.apache.org/jira/browse/CAY-1902 > Project: Cayenne > Issue Type: Improvement > Components: Core Library > Affects Versions: 3.2.M2 > Reporter: John Huss > Assignee: John Huss > Priority: Minor > Fix For: 3.2.M2 > > Attachments: 0001-Implement-db-path-evaluation-in-memory.patch > > > Expressions using db paths don't support in-memory evaluation against > DataObjects (there is a TODO in the code). -- This message was sent by Atlassian JIRA (v6.1.5#6160)