Hello there;

Can some body explain if this is the expected behavior,

I am reading a record for update (displayed on GUI). During this update process (before making final update call) I am trying to fetch all the records from the same table to which my record belongs, but before fetching this process is initially committing my object changes to Database and then fetching the whole table , so my object gets updated to database table even i f I have not made final update call. Can you tell me how can prevent this from happening?.

Thanks in advance :-)

The session will flush to ensure that you get fresh data from database, take a look in the nhibernate reference manual chapter 9.6.

One way to avoid this in your situation would be to evict the object to disable change-tracking for it before fetching the collection, but somehow that doesn't feel right

The normal approach here is to wrap the functionality within the session in a transaction so these writes can be done as required. If you want the whole change you commit, otherwise you roll back.

In the event that you don't want to roll back you can have some kind of compensation code that will re-modify the state of your object so it's back the way you want it before your commit.

Cheers,

Symon.