Can't attach on destroy events of cascaded delete about bookshelf-cascade-delete HOT 3 CLOSED

Wondering, why for the cascading destroying we can't just get the dependents list and for each using model.related().destroy() or map over them incase of model to destroy them?

That would make for a 1 more query on each cascade delete.

Rather then deleting children where foreign-key matches. We would fetch related data, map over them and destroy.

Could we somehow make it optional to delete with lifecycle hook?

from bookshelf-cascade-delete.

Hey @renarsvilnis!

So regarding your code snippets, the events are not triggered because this plugin does not fetch or even access the destroyed model's relations, it was only designed to execute delete queries for each dependent before executing its destroy method though the foreign key.

Regarding your suggestion, as you said that would make one more query for each dependent and its dependents, which seems totally unnecessary unless you want to benefit from the events.

I understand this can be useful as an option, although I don't think I'll have time to explore its solution in a near future so I encourage you to dive in and implement it. WDYT?

from bookshelf-cascade-delete.

I'm closing this issue for lack of activity.

@renarsvilnis give a shout if you come up for a solution for this feature.

from bookshelf-cascade-delete.