[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30531#action_30531 ]
Jörg von Frantzius commented on MAGNOLIA-3331: ---------------------------------------------- The provided patch applies to the 4.4 branch http://svn.magnolia-cms.com/svn/community/magnolia/branches/magnolia-4.4 > Provide for maxResultSize in Query-API > -------------------------------------- > > Key: MAGNOLIA-3331 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3331 > Project: Magnolia > Issue Type: Improvement > Components: core > Reporter: Jörg von Frantzius > Assignee: Philipp Bärfuss > Attachments: magnolia-core.patch > > > Currently when executing a query through the Magnolia query API, there is no > way of preventing the result set from being iterated completely. When e.g. > only the first couple of objects from a large result set are of interest, > then thousands of objects are instantiated unnecessarily, resulting in a huge > performance penalty. > These problems have been addressed in the [openmind Magnolia Criteria > API|http://www.openmindlab.com/lab/products/mgnlcriteria.html], but this > cannot be used e.g. for the STK implementation. > So in order to optimize e.g. the STK, the core query API must be extended. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------