mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
[PR #10398] Move runtime check for to-many associations in mapped superclasses to a more suitable place #12329
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?
Original Pull Request: https://github.com/doctrine/orm/pull/10398
State: closed
Merged: No
Closing this since #10473 was merged; it removed the check altogether.
This PR moves the check that a mapped superclass does not declare to-many associations to a more suitable (IMHO) place.
It is no longer checked when another class inherits the association from the mapped superclass, but at the final runtime validation stage when loading the metadata for the mapped superclass itself.
In addition to that, can we review whether the check is correct for the case where we have
In other words, only the mapped superclass may not define to-many associations, but it is fine if an entity class above it does and when an entity class below inherits all that? My feeling is that should be fine.