Subject fk problem
Author Lauri Zoova

It looks like foreign key constraints are checked in order they were
created. This can be a problem sometimes (created two scripts, one to
produce and other to solve this kind of problem). Also the current
firing order can not be checked.

Could the server be improved so, that it could solve the correct order
of executing foreign key cascades itself?

Or maybe the error message could include a hint to this when there was
unexecuted cascades at the time of fk violation.