The error below is caused for the following reason. I delete a row (via nhibernate) from a table called "callsign". that works, but causes a trigger to fire which deletes a row from another table (this needs to be a trigger for various reasons...the trigger does a lot). The effect is that NHibernate thinks 2 rows have been deleted instead of 1 (we delete by id). How can I tell NHibernate to ignore the row deleted by the trigger as part of it's error check...or do I have to catch this specific error message?

Hibernate version: 1.2 1.2



Full stack trace of any exception that occurs:EBUG Fatal Error , Source : NHibernate
DEBUG Fatal Error , Method : VerifyOutcomeNonBatched
DEBUG Fatal Error , Date : 3/31/2008
DEBUG Fatal Error , Time : 12:35:27 PM
DEBUG Fatal Error , Computer : ven-dev-web2
DEBUG Fatal Error , Error : Unexpected row count: 2; expected: 1
DEBUG Fatal Error , Stack Trace : at NHibernate.AdoNet.Expectations.BasicExpectation.VerifyOutcomeNonBatched(Int32 rowCount, IDbCommand statement)

Name and version of the database you are using: sql server 2005

If you are using SQL Server, you can add SET ROWCOUNT OFF at the start of the trigger.

thanks so much. It looks like Set Nocount On works as well. I finally found that in another post.

My bad. That's what I meant to say. What I actually said was complete nonsense.