mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
DDC-1225: Invalid SQL generated (extra comma) when joining to entity with composite PK #1540
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 (Jun 23, 2011).
Originally assigned to: @guilhermeblanco on GitHub.
Jira issue originally created by user darkangel:
$qb->from('Tournaments*Model*StageBracketTeamRegistration', 'r') ->innerJoin('r.teamSelection', 'ts') ->innerJoin('ts.players', 'tsp') ->select('r, ts, tsp') ->where('r.stageBracket = ?1') ->andWhere('r.opponentIsReserve = false') ->orderBy('r.registrationDateTime') ->setParameter(1, $bracket);Generates:
SELECT s0*.id AS id0, s0_.opponent_is_reserve AS opponent_is_reserve1, s0_.opponent_checked_in AS opponent_checked_in2, s0_.registration_date_time AS registration_date_time3, t1_.id AS id4,, s0_.type AS type5, s0_.stage_bracket_id AS stage_bracket_id6, s2_.team_selection_id AS team_selection_id7, t1_.team_id AS team_id8, t3_.team_selection_id AS team_selection_id9, t3_.player_id AS player*id10 FROM stage*bracket_team_registrations s2* INNER JOIN stage*bracket_registrations s0_ ON s2_.id = s0*.id INNER JOIN team*selections t1_ ON s2_.team_selection_id = t1*.id INNER JOIN team*selection_players t3_ ON t1_.id = t3_.team_selection*id WHERE s0*.stage_bracket_id = 22 AND s0_.opponent_is*reserve = 0 ORDER BY s0*.registration_date*time ASCNote the 2nd comma after "t1_.id AS id4". TeamSelectionPlayer uses a composite PK. I have attached the relevant entity classes.
@doctrinebot commented on GitHub (Jul 28, 2011):
Comment created by @beberlei:
Fixed
@doctrinebot commented on GitHub (Aug 12, 2011):
Comment created by darkangel:
Where can I find the changeset? Would it be easy for me to apply the changes to 2.1.0?
@doctrinebot commented on GitHub (Aug 12, 2011):
Comment created by darkangel:
No worries, found the changes here:
196632978c@doctrinebot commented on GitHub (Aug 13, 2011):
Comment created by darkangel:
This is still an issue:
\
Results in:
@doctrinebot commented on GitHub (Aug 14, 2011):
Comment created by @guilhermeblanco:
Hi,
I attempted to create a failing test case for this issue, but either the provided entities are not enough or the issue is not reproducible anymore (it was already fixed in latest 2.2-DEV).
Could you please try to compile everything into a test case?
Cheers,
@doctrinebot commented on GitHub (Aug 15, 2011):
Comment created by darkangel:
Hi Guilherme,
I'll attach 2 simple entities for testing. You can run the following query:
\
I'm running this against 2.1.0 + this change.
Thanks.
@doctrinebot commented on GitHub (Aug 15, 2011):
Comment created by @guilhermeblanco:
Fixed in this commit
6857134f36Thanks for the report!
@doctrinebot commented on GitHub (Aug 15, 2011):
Issue was closed with resolution "Fixed"
@doctrinebot commented on GitHub (Aug 29, 2011):
Comment created by @beberlei:
Merged into 2.1.x