Bug #159
Projection query not working correctly on query method pagination
| Status: | Closed | Start: | 11/09/2009 | |
|---|---|---|---|---|
| Priority: | Highest | Due date: | ||
| Assigned to: | % Done: | 100% |
||
| Category: | Core DAO | Spent time: | - | |
| Target version: | 1.1 |
Description
When using Pageable parameters on query methods the query calculating the total amount of results (without paging) does not project on count correctly. The query is fired as is and thus returns the entire dataset which is quite resource consuming especially on larger datasets.
Associated revisions
- added method to create counting queries from standard ones
- references #159
- extended
HadesQueryto also return a counting query - extended implementations accordingly
- extended
QueryMethodto get anQueryExtractor, too - references #159
- extended
QueryExtractorinterface to allow asking if the extractor is actually able to extract query strings fromQueryinstances - references #159
- assert that we can extract the query string in case we have a paged query
- references #159
- use the count projected query to lookup the actual number of elements
- fixes #159
History
Updated by Oliver Gierke 9 months ago
- Priority changed from High to Highest
Updated by Oliver Gierke 9 months ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Status geƤndert durch Changeset r7862.
Updated by Oliver Gierke 8 months ago
- Status changed from Fixed to Closed