[PR #1146] Allow orderBy to reference associations #9202

New Issue

admin · 2026-01-22T16:03:33+01:00

admin commented

2026-01-22 16:03:33 +01:00

Original Pull Request: https://github.com/doctrine/orm/pull/1146

State: closed
Merged: Yes

If I specify an order-by clause on a to-many association, e.g. @OrderBy({"foo" = "ASC"}), where foo is a to-one-association on the target entity, the collection is sorted by foo_id (this behaviour is implemented in BasicEntityPersister::getOrderBySQL()).

This works fine. However, Doctrine\ORM\Tools\SchemaValidator complains that foo is not a field.

This change makes the validator accept order-by clauses on associations where the target entity is the owning side, and the association is single-valued (AFAICT this is the same restrictions that BasicEntityPersister uses).

**Original Pull Request:** https://github.com/doctrine/orm/pull/1146 **State:** closed **Merged:** Yes --- If I specify an order-by clause on a to-many association, e.g. `@OrderBy({"foo" = "ASC"})`, where foo is a to-one-association on the target entity, the collection is sorted by foo_id (this behaviour is implemented in BasicEntityPersister::getOrderBySQL()). This works fine. However, Doctrine\ORM\Tools\SchemaValidator complains that foo is not a field. This change makes the validator accept order-by clauses on associations where the target entity is the owning side, and the association is single-valued (AFAICT this is the same restrictions that BasicEntityPersister uses).

admin added the pull-request label 2026-01-22 16:03:33 +01:00

admin referenced this issue

2026-01-22 16:10:46 +01:00

[PR #9202] Add SchemaIgnoreClasses property #11429

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#9202