In my application users cannot truly delete records. Rather, the record’s Deleted field gets set to 1, which hides it from selects.
I need to maintain this behaviour and I’m looking into whether NHibernate is appropriate for my app. Can I override NHibnernate’s delete behaviour so that instead of issuing DELETE statements, it issues UPDATES, as described above?
I would obviously also need to override its SELECT behaviour to include the ‘AND Deleted = 0‘ clause. Or read from a view instead. I’m not sure.
I think the best way to get such behaviour would be by implementing the IInterceptor interface which would allow you to perform your own code as shown within the NHibernate Documentation.
Otherwise, you could simply create a trigger on delete that would perform an update. This solution is simpler, but is this suitable for your needs?
As for the SELECT, you only need to write method that will use Criterion with a Where clause to specify the Deleted=0 thing.