I am using nhibernate in a quite big project.The system has a settings table which has 10 columns and one row, there is always a row and it should not be deleted only modified.Concurrency can be a problem as many clients can increment columns in the table like LastReceiptId.I'm thinking, it can't be a good idea to use nhibernate to solve this.With raw sql I can use a transaction and lock the table with for example: With (TABLOCKX, HOLDLOCK) while I select and update the LastReceiptId.Do you have any reasons to use or not use nhibernate in a situation like this?
Should I use nhibernate for a one row settings table
c#;orm;nhibernate