mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
DDC-2475: ORDER BY on existing column is added, not replaced #3108
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 (May 28, 2013).
Jira issue originally created by user jeremylivingston:
It seems that if an entity has an existing ORDER BY clause on a relation that any subsequent ORDER BYs on that field are added instead of replaced.
For example, I have two entities: Person and Membership. Person.Memberships has the following clause specified:
@ORM\OrderBy({"createDate" = "DESC"})
I also have a repository method that uses this relationship and sets the following DQL:
SELECT person, m
FROM \Company\Person person
JOIN person.memberships m
ORDER BY m.createDate ASC
I would expect this query to replace the existing ORDER BY with ORDER BY m.createDate ASC. Instead, it adds the ORDER BY to the existing one, which makes the end result: ORDER BY m.createDate ASC, m.createDate DESC.
This is obviously causing an issue since you can't sort by the same column in different order. Is this behavior by design? If so, is there a way to override the existing ORDER BY setting?
@doctrinebot commented on GitHub (Jun 5, 2013):
Comment created by @FabioBatSilva:
Fixed :
753d63c2d4@doctrinebot commented on GitHub (Jun 5, 2013):
Issue was closed with resolution "Fixed"