DDC-858: orderBy on associations does not work with discriminator columns #1063

New Issue

admin · 2026-01-22T13:00:43+01:00

admin commented

2026-01-22 13:00:43 +01:00

Originally created by @doctrinebot on GitHub (Nov 5, 2010).

Originally assigned to: @guilhermeblanco on GitHub.

Jira issue originally created by user sebastian.hoitz:

When you specify a oneToMany or manyToMany association to be ordered by a discriminator column, Doctrine fails, giving this error:

C:\Users\Sebastian Hoitz\Documents\Entwicklung\kt_api\trunk\tools>doctrine orm:validate-schema
[Mapping] FAIL - The entity-class 'App_Model_Contact' mapping is invalid:

The association App_Model_Contact#attributes is ordered by a foreign field type that is not a field on the target entity App_Model_Contact_Attribute

But in some cases (think of attributes, for example) you would really need this.

Originally created by @doctrinebot on GitHub (Nov 5, 2010). Originally assigned to: @guilhermeblanco on GitHub. Jira issue originally created by user sebastian.hoitz: When you specify a oneToMany or manyToMany association to be ordered by a discriminator column, Doctrine fails, giving this error: C:\Users\Sebastian Hoitz\Documents\Entwicklung\kt_api\trunk\tools>doctrine orm:validate-schema [Mapping] FAIL - The entity-class 'App_Model_Contact' mapping is invalid: - The association App_Model_Contact#attributes is ordered by a foreign field type that is not a field on the target entity App_Model_Contact_Attribute But in some cases (think of attributes, for example) you would really need this.

admin added the New Feature label 2026-01-22 13:00:43 +01:00

admin closed this issue

2026-01-22 13:00:44 +01:00

admin commented

2026-01-22 13:00:45 +01:00

@doctrinebot commented on GitHub (Nov 5, 2010):

Comment created by sebastian.hoitz:

Changing ClassMetadataInfo::hasField to this would fix the issue:

public function hasField($fieldName)
{
    return isset($this->fieldMappings[$fieldName]) ](| $this->discriminatorColumn['name') == $fieldName;
}

But I'm not sure if this is the most elegant solution.

Correction: This only solves the doctrine orm:schema-validate error. It does not order correctly :(

@doctrinebot commented on GitHub (Nov 5, 2010): Comment created by sebastian.hoitz: Changing ClassMetadataInfo::hasField to this would fix the issue: ``` public function hasField($fieldName) { return isset($this->fieldMappings[$fieldName]) ](| $this->discriminatorColumn['name') == $fieldName; } ``` But I'm not sure if this is the most elegant solution. Correction: This only solves the doctrine orm:schema-validate error. It does not order correctly :(

admin commented

2026-01-22 13:00:46 +01:00

@doctrinebot commented on GitHub (Oct 16, 2011):

Comment created by @guilhermeblanco:

Discriminator columns should never be used from user perspective. Discriminators are a internal helper for ORM only.

If you want to achieve a similar thing, you should add your own type field and track it for yourself.

@doctrinebot commented on GitHub (Oct 16, 2011): Comment created by @guilhermeblanco: Discriminator columns should never be used from user perspective. Discriminators are a internal helper for ORM only. If you want to achieve a similar thing, you should add your own type field and track it for yourself.

admin commented

2026-01-22 13:00:48 +01:00

@doctrinebot commented on GitHub (Oct 16, 2011):

Issue was closed with resolution "Invalid"

@doctrinebot commented on GitHub (Oct 16, 2011): Issue was closed with resolution "Invalid"

admin referenced this issue

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

[PR #1063] [MERGED] singularize variable name on add/remove methods for EntityGenerator #9109

admin referenced this issue

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

[PR #1063] singularize variable name on add/remove methods for EntityGenerator #9113

Sign in to join this conversation.