RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2024-12-14 07:06:04 +03:00
Code Issues Projects Releases Wiki Activity

Improved error messages in Paginator: LimitSubqueryOutputWalker

Browse Source 
The already existing follow-up check throwing "Not all identifier properties can be found in the ResultSetMapping: %s" is a much more technical description.

If $sqlIdentifier is empty (count 0) it can be concluded that there are no mapped results. An alternative error message could thus be "The Paginator does not support queries without mapped results." (line 153).

Possibly '!=' on line 154 could be replaced by '>' because i think this is the only situation that can occur. But since i don't know this for sure, i left it like i found it.
This commit is contained in:
flip111 2013-09-17 15:07:08 +02:00
parent fe78977973
commit b803f06c8f
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
lib/Doctrine/ORM/Tools/Pagination/LimitSubqueryOutputWalker.php
View File

@ -149,7 +149,9 @@ class LimitSubqueryOutputWalker extends SqlWalker
} }
} }
if (count($rootIdentifier) != count($sqlIdentifier)) { if (count($sqlIdentifier) === 0) {
throw new \RuntimeException('The Paginator does not support Queries which only yield ScalarResults.');
} elseif (count($rootIdentifier) != count($sqlIdentifier)) {
throw new \RuntimeException(sprintf( throw new \RuntimeException(sprintf(
'Not all identifier properties can be found in the ResultSetMapping: %s', 'Not all identifier properties can be found in the ResultSetMapping: %s',
implode(', ', array_diff($rootIdentifier, array_keys($sqlIdentifier))) implode(', ', array_diff($rootIdentifier, array_keys($sqlIdentifier)))