Open iamonkara opened 1 year ago
hi!
this gem does not take special care of DB constraints.
it basically just piggy-backs on active_records dependent:
option and triggers at the same time as e.g. dependent: :destroy
.
as a result, it should only run into trouble in the same scenarios where a (full chain of) dependent: :destroy
callbacks would also run into trouble, if i'm not mistaken.
its a bit hard to tell what's going wrong without knowing the exact setup of relations and full stacktrace.
edit: actually what i said above is not universally true because delete_recursively
deletes stuff in the relation tree depth-first after the first record is deleted, whereas dependent: :destroy
proceeds breadth-first, so it might make a difference when it comes to constraints and perhaps this "traversal strategy" should be configurable.
I get these errors on a
has_one
andbelongs_to
association