How to disable engaging parent/child table per class deletions

[Michael Powell]

Hello,

I have a case via Fluent NHibernate whereby I am extending a base class via a subclass mapping:

Extends<MyBaseClass>();

This ends up being a <joined-subclass> in Hbm.Xml speak.

I want for the database to handle its own book keeping after deletion is detected on the child table, which subsequently deletes from the parent table.

The competing argument is to let the ORM do its work.

How hard would it be to instruct the ORM one way or the other? Via Fluent, that might look something like this:

Extends<MyBaseClass>().Triggers.AfterDelete(Triggers.NoAction);

Or something like that (TBD).

Regards,

Michael Powell