#1210: Selected field with alias is not recognized
-----------------------------------+--------------------------------------- -
 Reporter:  Max_Schreck            |       Owner:  romanb
     Type:  defect                 |      Status:  new  
 Priority:  minor                  |   Milestone:  0.11.1
Component:  Query/Hydration        |     Version:  0.11  
 Keywords:                         |    Has_test:  0    
 Mystatus:  Pending Core Response  |   Has_patch:  0    
-----------------------------------+--------------------------------------- -
 {{{
 Doctrine_Query::create()
     ->select('up.name up_name, u.name')
     ->from('UserProfile up')
     ->innerJoin('up.User u')
     ->execute();
 }}}

 This query throws Doctrine_Query_Exception with message "The root class of
 the query (alias up) must have at least one field selected.".

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1210>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper

#1210: Selected field with alias is not recognized
------------------------------+-------------------------------------------- -
  Reporter:  Max_Schreck      |       Owner:  romanb              
      Type:  defect           |      Status:  closed              
  Priority:  minor            |   Milestone:  0.11.1              
 Component:  Query/Hydration  |     Version:  0.11                
Resolution:  wontfix          |    Keywords:                      
  Has_test:  0                |    Mystatus:  Pending Core Response
 Has_patch:  0                |  
------------------------------+-------------------------------------------- -
Changes (by romanb):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 You cant alias field/property names. This would be like changing
 field/property names on the fly. Your classes have a defined and fixed set
 of fields/properties. The only thing that can be aliases in DQL queries
 are artificial scalar values that result from aggregate functions for
 example.

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1210#comment:1>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper

#1210: Selected field with alias is not recognized
------------------------------+-------------------------------------------- -
  Reporter:  Max_Schreck      |       Owner:  romanb              
      Type:  defect           |      Status:  closed              
  Priority:  minor            |   Milestone:  0.11.1              
 Component:  Query/Hydration  |     Version:  0.11                
Resolution:  wontfix          |    Keywords:                      
  Has_test:  0                |    Mystatus:  Pending Core Response
 Has_patch:  0                |  
------------------------------+-------------------------------------------- -
Comment (by Max_Schreck):

 OK but if I can't alias field names it shouldn't let me do it. If I remove
 "u.name" from the select statement above, the query is processed
 correctly, and the first aliased field "up_name" is properly returned in a
 result. So it is a bit misleading.

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1210#comment:2>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper

#1210: Selected field with alias is not recognized
------------------------------+-------------------------------------------- -
  Reporter:  Max_Schreck      |       Owner:  romanb              
      Type:  defect           |      Status:  closed              
  Priority:  minor            |   Milestone:  0.11.1              
 Component:  Query/Hydration  |     Version:  0.11                
Resolution:  wontfix          |    Keywords:                      
  Has_test:  0                |    Mystatus:  Pending Core Response
 Has_patch:  0                |  
------------------------------+-------------------------------------------- -
Comment (by romanb):

 You are right, thats mainly a problem of the current DQL parser which is
 far from accurate when it comes to accepting/declining certain input.
 If you're interested in what is on the agenda for hydration & DQL in 2.0
 this might interest you: http://trac.phpdoctrine.org/wiki/NewHydration

 Although 2.0 is far away we plan to backport the scalar hydration modes to
 1.0. But the special SCALAR() DQL function will most likely not be
 backported.
 So in 2.0 you will be able to do sth like this: select scalar(up.name)
 up_name ... The resulting scalar value will not be put into any objects
 however, as you can see in the link above.

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1210#comment:3>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper

#1210: Selected field with alias is not recognized
------------------------------+-------------------------------------------- -
  Reporter:  Max_Schreck      |       Owner:  romanb              
      Type:  defect           |      Status:  closed              
  Priority:  minor            |   Milestone:  0.11.1              
 Component:  Query/Hydration  |     Version:  0.11                
Resolution:  wontfix          |    Keywords:                      
  Has_test:  0                |    Mystatus:  Pending Core Response
 Has_patch:  0                |  
------------------------------+-------------------------------------------- -
Comment (by Max_Schreck):

 Thank you for the explanation. I'll take a look on that article. :)

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1210#comment:4>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper