Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Trivial
-
Resolution: Unresolved
-
Affects Version/s: 2.1.6
-
Fix Version/s: None
-
Component/s: ORM
-
Labels:None
Description
I made the assumption that the way to define a cascading delete is to do (in YAML):
cascade: [delete]
When it is actually:
cascade: [remove]
It would be nice if Doctrine would throw an exception when the user sets a cascade option which does not exist.