DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-1050
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus Core

Query "cache key" used for determining if a query is different (for the purposes of caching) doesn't allow for different FetchPlan

Created: 12/Jun/13 11:09 AM   Updated: 27/Jun/13 04:39 PM   Resolved: 12/Jun/13 11:11 AM
Component/s: Queries
Affects Version/s: 2.1.4, 2.2.4, 3.0.11, 3.1.5, 3.2.4
Fix Version/s: 3.2.5

 Description  « Hide
Needs to allow for whether the FetchPlan is different too, for example if one usage has some FetchGroup enabled and in another it isn't then this likely means different fields selected for the query, hence a different datastore query

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 12/Jun/13 11:11 AM
SVN trunk fixes this, adding FetchPlan.toString() to the end of the cache query key