Build eager loading tree when doing cascaded delete

[TimothyBJacobs]

[TimothyBJacobs]

This is going to be pretty complicated. We'd have to iterate over all registered tables to find which ones have references to the table of the model currently being deleted. This would have to be done in a recursive fashion as well.

A better way to do this would probably be to utilize a directed Graph to store the relationships between delete constrains. That should allow for better traversal and make it easier to build the eager loading data.

Another challenge, albeit simpler to solve, is that once the results have been "eager-loaded" to use those results instead of following the regular cascading process.