Without looking at the code at all, is this something that could start to be blended? I think we all agree that minimizing the differences between server and client functionality is necessary. If it could actually be enforced by using the same code, all the better.
-- Kevin On 1/20/08 11:33 AM, "Andrus Adamchik (JIRA)" <[email protected]> wrote: > Caching doesn't work for paginated queries > ------------------------------------------ > > Key: CAY-967 > URL: https://issues.apache.org/cayenne/browse/CAY-967 > Project: Cayenne > Issue Type: Bug > Components: Cayenne Core Library > Affects Versions: 1.2 [STABLE], 2.0 [STABLE], 3.0 > Reporter: Andrus Adamchik > Assignee: Andrus Adamchik > Fix For: 3.0 > > > The order of execution in DataContextQueryAction.execute is this > > 1. interceptPaginatedQuery > 2. interceptOIDQuery > 3. interceptRelationshipQuery > 4. interceptRefreshQuery > 5. interceptLocalCache > > The order in CayenneContextQueryAction (ROP) is this: > > > 1. interceptOIDQuery > 2. interceptRelationshipQuery > 3. interceptRefreshQuery > 4. interceptLocalCache > 5. interceptPaginatedQuery > > > I.e. we allow caching of paginated lists in ROP, but not in regular Cayenne... > This makes no sense to me, so I am going to change DataContextQuery action to > match CayenneContextQueryAction
