Home/ Questions/Q 8982867
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T20:41:13+00:00

Given: Two custom classes in Magento with a Many-to-One relationship between them. The child

  • 0

Given:

Two custom classes in Magento with a Many-to-One relationship between them.
The child holds a foreign key to the parent.
The database is set to cascade deletes.

There are cases when a child’s reference changes to a different parent. In some of those cases, I want to delete the parent in the afterSave method of the child. When I do this, the child itself disappears, since the change of FK to the new parent hasn’t been written to the database yet, and the database level cascade kicks in.

How can I arrange for the deletion of the parent object after the write of the new foreign key in the child object?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    afterSave triggers before the query has been written to DB, as you’ve noticed yourself. You need to use *_save_commit_after event. Where asterisk is your Models event_prefix. Create an Observer and listen for this event, that way you can be sure that info in DB has been already updated, and you won’t suffer the foreign key effect.

    • 0