http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DDC-1927 Doctrine 2 - ORM <p>When paginating a DQL string which selects specific fields it results in the following error: PHP Fatal error: Uncaught exception 'RuntimeException' with message 'Not all identifier properties can be found in the ResultSetMapping: id'</p> <p>NOT working: 'SELECT c.id, c.number FROM Application\Entity\Course c'<br/> WORKING: 'SELECT c FROM Application\Entity\Course c'<br/> WORKING: 'SELECT c, c.id, c.number FROM Application\Entity\Course c'</p> <p>Setting hydration mode to scalar results makes no difference.</p> <p>Gist to example code and stack trace: <a href="https://gist.github.com/d5cd6d0b0ac28e722dd7" class="external-link">https://gist.github.com/d5cd6d0b0ac28e722dd7</a></p> DDC-1927

Pagination of a SELECT of specific fields results in a RuntimeException

Bug Major Resolved Can't Fix All Benjamin Eberlei Zacharias Luiten paginator Mon, 16 Jul 2012 10:10:55 +0000 Thu, 18 Apr 2013 20:22:25 +0000 Sun, 25 Nov 2012 12:23:36 +0000 Git Master ORM 0 5 <p>First results: This is very complicated to support, the pagination was designed for entity results. I have to check this when I have more time.</p> <p>Hi Benjamin,<br/> I can change my code to select entity results (even for hundreds/thousands results).<br/> But for now Pagination is not usable with ResultSetMapping::addScalarResult </p> <p>The reason this error occurs is because the Paginator creates its own ResultSetMapping and relies on the SqlWalker to configure it (see Doctrine\ORM\Query\SqlWalker::walkSelectExpression).</p> <p>Doctrine will interpret each field in the first example (SELECT c.id, c.number...) as a PathExpression and add it to the result set mapping as a scalar result. This makes it impossible for the paginator to reliably know which field can be considered an identifier.</p> <p>A quick fix might be to re-write the query to use PartialObjectExpression: SELECT partial c.</p> {id, number} <p> ...</p> <p>(edited after a re-read and realization that a custom ResultSetMapping wouldn't cut it)</p> <p>Allowing generic+complex pagination on scalar results is impossible for us, closing as can't fix. </p> <p>Just use LIMITs yourself here or as suggested partial objects.</p> <p>imho this pagination feature is quite useless if we are forced to fetch the complete Entity. Take for example a big table with a lot of data: extracting all the infos will take a lot of time... There should be a way to support the first query type</p>