I've just run across what appears to be a bug in RC1 - I'm going to test in RC2 soon, however I thought I'd post here just in case.

I have a table-per-subclass mapping where one of the properties in the subclass allows nulls while the table that the subclass maps to does not.

When an insert is performed a record is inserted in the base class table and then an exception is thrown when attempting to insert the record into the sub-class table - as expected.

The issue is that the record in the base class table is not rolled back when the exception is thrown - is this by design or a bug?

Cheers,

Symon.

I would say it's by design - NH assumes that entire current transaction will be rolled back in case of any problems.

Ta Sergey!

Symon.