mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
DDC-337: Add ORDER BY clause to collection persister SQL generation #416
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 (Feb 14, 2010).
Originally assigned to: @beberlei on GitHub.
Jira issue originally created by user @beberlei:
OrderBy Mapping information of collections translate to an ORDER BY clause in the Collection Persister for both OneToMany and ManyToMany associations.
@doctrinebot commented on GitHub (Feb 14, 2010):
Comment created by @beberlei:
Implemented for both ManyToMany and OneToMany associations.
@doctrinebot commented on GitHub (Feb 14, 2010):
Issue was closed with resolution "Fixed"
@doctrinebot commented on GitHub (Feb 15, 2010):
Comment created by romanb:
Is there a test for class table inheritance already? JoinedSubclassPersister#_getSelectEntitiesSql might need to be adjusted for this feature also. We should add a test to make sure.
@doctrinebot commented on GitHub (Feb 15, 2010):
Comment created by @beberlei:
Oh no there is no test for class table inheritance,it probably fails.
@doctrinebot commented on GitHub (Feb 15, 2010):
Comment created by @beberlei:
Wah this could be a considerable issue of the implementation, how to make sure %alias% is replaced with the correct alias in a class table hierachy?
@doctrinebot commented on GitHub (Feb 15, 2010):
Comment created by @beberlei:
Changed @OrderBy to take a simple DQL snippet and parse this according to very strict rules. This solves the class table inheritance problem as shown by a new test-case