DDC-138: Allow for mixed inheritance mapping #173

Closed
opened 2026-01-22 12:29:32 +01:00 by admin · 5 comments
Owner

Originally created by @doctrinebot on GitHub (Nov 12, 2009).

Originally assigned to: @Ocramius on GitHub.

Jira issue originally created by user reinier.kip:

Requesting implementation of mixed inheritance mapping (class table inheritance and single table inheritance).

This would be especially handy when the difference between certain classes is only "implementational" (i.e. a subclass only functions differently/implements abstract methods and does not specify any additional fields). Using class table inheritance would result in tables only containing an id column.

Originally created by @doctrinebot on GitHub (Nov 12, 2009). Originally assigned to: @Ocramius on GitHub. Jira issue originally created by user reinier.kip: Requesting implementation of mixed inheritance mapping (class table inheritance and single table inheritance). This would be especially handy when the difference between certain classes is only "implementational" (i.e. a subclass only functions differently/implements abstract methods and does not specify any additional fields). Using class table inheritance would result in tables only containing an id column.
admin added the New FeatureWon't Fix labels 2026-01-22 12:29:32 +01:00
admin closed this issue 2026-01-22 12:29:33 +01:00
Author
Owner

@doctrinebot commented on GitHub (Nov 12, 2009):

@doctrinebot commented on GitHub (Nov 12, 2009): - is duplicated by [DDC-265: Possibility for Nested Inheritance](http://www.doctrine-project.org/jira/browse/DDC-265)
Author
Owner

@malukenho commented on GitHub (Jan 5, 2017):

@Ocramius is someone still needs this feature?

@malukenho commented on GitHub (Jan 5, 2017): @Ocramius is someone still needs this feature?
Author
Owner

@Ocramius commented on GitHub (Jan 5, 2017):

No, this is an edge case that can probably be fixed via custom persisters and hydrators instead.

Also, @guilhermeblanco is adding table information to every column now, so mixed inheritance will kinda come out of the box in ORM v3, if all works out as expected.

@Ocramius commented on GitHub (Jan 5, 2017): No, this is an edge case that can probably be fixed via custom persisters and hydrators instead. Also, @guilhermeblanco is adding table information to every column now, so mixed inheritance will kinda come out of the box in ORM v3, if all works out as expected.
Author
Owner

@nkamuo commented on GitHub (Apr 6, 2024):

Hello @Ocramius! Is there any hope of having this on doctrine v3?

@nkamuo commented on GitHub (Apr 6, 2024): Hello @Ocramius! Is there any hope of having this on doctrine v3?
Author
Owner

@Ocramius commented on GitHub (Apr 6, 2024):

@nkamuo I'm no longer actively maintaining here

@Ocramius commented on GitHub (Apr 6, 2024): @nkamuo I'm no longer actively maintaining here
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#173