DDC-1972: Throw an exception when setting cascade options which do not exist #2487

Open
opened 2026-01-22 13:55:03 +01:00 by admin · 0 comments
Owner

Originally created by @doctrinebot on GitHub (Aug 8, 2012).

Originally assigned to: @Majkl578 on GitHub.

Jira issue originally created by user gzankevich:

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.

Originally created by @doctrinebot on GitHub (Aug 8, 2012). Originally assigned to: @Majkl578 on GitHub. Jira issue originally created by user gzankevich: 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.
admin added the Improvement label 2026-01-22 13:55:03 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#2487