#1397: left/innerJoin on non-related classes
-----------------------------------+----------------------------------------
 Reporter:  colnector              |       Owner:  romanb
     Type:  enhancement            |      Status:  new   
 Priority:  major                  |   Milestone:  New   
Component:  Query/Hydration        |     Version:  1.0   
 Keywords:                         |    Has_test:  0     
 Mystatus:  Pending Core Response  |   Has_patch:  0     
-----------------------------------+----------------------------------------
 Trying to execute a JOIN when a relation has not been defined is producing
 'unknown relation alias' error.

 Topic was discussed here: http://www.doctrine-
 project.org/forum/viewtopic.php?f=2&t=134

 Here's another example of when it's useful to have JOINs when relations
 are not defined.

 class User(id,name)
 class UserExtraData(user_id, extra_data1, extra_data2)

 The reason for 2 classes is that most users do not have that extra data
 and so it'll burden the database to use the same table.

 Now say I have
 class GroupUser(group_id, user_id)

 And from this class I wish to get to the extra data. My two current
 options are:
 1/ Use 2 joins
 2/ Create another relation between EVERY class that relates to User so
 it'll relate to UserExtraData as well.

 IMHO - both these options are not as good as simply having a nice JOIN
 between GroupUser and UserExtraData when it is needed.

-- 
Ticket URL: <http://trac.doctrine-project.org/ticket/1397>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"doctrine-svn" group.
 To post to this group, send email to [email protected]
 To unsubscribe from this group, send email to [EMAIL PROTECTED]
 For more options, visit this group at 
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---

Reply via email to