-
Type: Task
-
Resolution: Done
-
Affects Version/s: None
-
Component/s: None
Very similar to issue MONGOID-1117 but only happens on the childs own after_destroy callback (before_destroy is not affected).
Is somehow not triggered when using destroy_all for some reason which was weird so I included that example in the gist.
Reproduce with:
https://gist.github.com/1149078
Introduced in 2.1.8 (I think).