Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.2
-
Component/s: None
-
Security Level: All
-
Labels:None
Description
The order of the DQL Select clause should matter for the result hydration:
SELECT u.id, u, u.name FROM User u => result keys: id, 1, name SELECT u.id, u.id FROM User u => result keys: id, or numerical hydration 0, 1 SELECT u.id, u AS user FROM User u => result keys: id, user
Issue Links
- is referenced by
-
DDC-1096
"You may have observed that in a mixed result, the object always ends up on index 0 of a result row."
-
Activity
Benjamin Eberlei
made changes -
Guilherme Blanco
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Benjamin Eberlei
made changes -
| Workflow | jira [ 13089 ] | jira-feedback [ 15063 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback [ 15063 ] | jira-feedback2 [ 16927 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback2 [ 16927 ] | jira-feedback3 [ 19180 ] |
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
- Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=DDC-1424, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
Implemented!!!
https://github.com/doctrine/doctrine2/commit/81cc6d9da83d217ea62bd467053fd9885d1083cd