Hi,

I noticed that the NHibernate 2.0 breaking changes list states that all database operations have to be within a transaction.

I am using some code that previously used NHibernate 1.2. There are queries etc. that are not wrapped within a transaction, yet they still seem to work.

The application uses ASP .NET and a custom HttpModule for referencing the session. I would appreciate some advice about what modifications are needed for this existing code.

Cheers,

James

In Hibernate 2.0 you cannot take advantage of "contextual sessions" on a managed environment, so your options for ensuring that every DB operation is wrapped in a transaction are:

-writing wrapping transaction code manually each time

-creating a base Data Access class, which all your DAO classes will extend, and which has basic insert(bean) delete(id) update(bean) executeSelect(SQL) methods, and inside each of those methods one session is obtained with Threadlocal and a transaction is created/begun/commited/trycached.

Hi,

Thanks for the reply Gonzalo. I was wondering what the possible consequences of executing queries outside a transaction might be? The existing code still seems to work but I have not had time to fully test it. There is quite a lot of code that will need to be changed.

BTW, as I am using ASP .NET the NHibernate session is created on each HTTP request so I didn't need to manually declare it as threadlocal.

Cheers,

James