Hi,

The examples in the NH documentation show the transaction being started before any object properties are updated. Is this a mandatory requirement or is it acceptable to load objects, update properties and then call BeginTransaction followed by Commit to update all the changed objects as part of a single transaction?

My understanding is that the BeginTransaction really acts as a wrapper for an ADO transaction so it would seem that there is no need to start the NH transaction until just before you want to commit all of the changes made in the session...is that right or are there other things that occur as part of the BeginTransaction call?

Thanks,

Jason

I would recommend you to start the transaction before doing any save() or update(). In fact, it would not be very correct if some flush (i.e. a query :-/) occurred although no tx was started.

If you use the persist() method instead of save(), one guaranty is that no query will be issued until there's a tx context (cf. Java Persistence with Hibernate book).

UPDATE : I just noticed I was in the NHibernate forum, not the hibernate one. So I guess my second paragraph does not apply, but still the first one.

OK...I am starting the transaction before calling Save or Update so it sounds like things are OK.

Yes, I have already stumbled across the problem of unexpected flushing that commits half finished changes to the DB and I have set Session.FlushMode = Commit globally in the application to prevent this from happening.

However, I never did get a response to my other post about the FlushMode...do you have any thoughts about this: http://forum.hibernate.org/viewtopic.php?t=966735&highlight=

Thanks for your help.

Jason