mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
DDC-799: Limit the number of Left Joins in a "JOINED" inheritance #983
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Sep 10, 2010).
Jira issue originally created by user noldor:
Hello , in our system we have entity like this:
/****
*/
class SiteObject { ..... }
If we use the entity SiteObject in a DQL it generates a SQL with left joins to all these 25 entities (as described in the MainEntity Discriminator Map).
Is it possible to explictly state the tables we want to make left join with ?
( In the future all of these tables are planned to grow very big.)
@doctrinebot commented on GitHub (Sep 10, 2010):
Comment created by @beberlei:
Dont use joined table inheritance in this case, it will blow your project.
It doesnt seem that the objects have any conceptual context that would make joined inheritance even interesting for all those objects.
@doctrinebot commented on GitHub (Sep 10, 2010):
Comment created by noldor:
Thank you for the reply ,
Through site_objects we handle things like file_uploads ( we have site_object_files , instead of article_files, author_files etc) , tagging of content ( site_object_tags) and other commonly used relations between tables.
At the same time, our system has grown in complexity and we rely heavily on this table to handle more complex object associations.
Could you please show us a more convenient approach in this scenario ( it's really not possible to abandon the 'site_objects' table at this stage)
Thank you in advance
@doctrinebot commented on GitHub (Sep 30, 2010):
Comment created by @beberlei:
Not an issue.
@doctrinebot commented on GitHub (Sep 30, 2010):
Issue was closed with resolution "Invalid"