For example, perhaps something in the following call(s):
I'd like to let the database handle the "abstraction" as I mentioned,
but I wonder if something like a SqlDelete() would be more appropriate
than letting NHibernate determine the classes/tables that require
As a last resort I will take the after delete trigger out of the child
class triggers, but only as a last resort, as I believe the database
should be handling this sort of integrity, with the ORM being a thin
vernier, best case.