[CAY-1585] SelectQuery automatic cache key needs FetchOffset

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.1M2
• Fix Version/s: 3.1M3, 3.0.3
• Component/s: Core Library
• Assignee: Dzmitry Kazimirchyk
• Reporter: Pedro Aquilino Sánchez
• Created: 02/Jul/11 16:47
• Updated: 03/Aug/11 11:19
• Resolved: 07/Jul/11 10:22

Description

SelectQueryMetadata.resolve:

Must include the fetchOffset property from query.
So we can cache correctly pagination queries.

for example without this property:

SelectQuery query = new SelectQuery(Example.class);
query.setCacheStrategy(QueryCacheStrategy.SHARED_CACHE);
query.setFetchOffset(0);
query.setFetchLimit(10);
ctx.performQuery(query);
// Returns the first ten elements, cached under key "Example/10"

Select query2 = new SelectQuery(Example.class);
query2.setCacheStrategy(QueryCacheStrategy.SHARED_CACHE);
query2.setFetchOffset(10);
query2.setFetchLimit(10);
ctx.performQuery(query2);
// Returns the first ten elements from cache, this is not correct it must return the next block of elements.
// Because the cache key is again "Example/10"