Hi this is a general question about NHibernate 1.2...

I want to save an object, but I do not want the INSERT command to occur before the session.Flush()...


I tried setting the Session.FlushMode to FlushMode.Never, but it still onvokes an INSERT command immediately.

how can I control this?

Are you concerned because you see an SQL statement in the debug or console? That doesn't necessarily mean that the SQL statement has been actually committed to the database.

Do you see an actual record inserted in the table?

If you're using database generated identifiers an insert will occur before you call flush because NHibernate needs to get the Id of the entity from the database. If you want to avoid this you can use NHibernate or user generated identifiers, however it shouldn't matter as long as you have a transaction that you can roll back.

Cheers,

Symon.

These are both helpful clues.

#1. if you use <generator class="identity" />, an INSERT command will happen immediately after the Save(..) call, this is by design, because the ID is assigned to the SCOPE_IDENTITY.

#2. you should not care when the insert occurs... If your session is properly wrapped inside of a transaction, the insert is not committed until the transaction is committed.


This alone is a good reason to use transactions with ANY session interaction, it gives you a higher degree of control over your database interactivity.

thanks guys!