Hi,

this is a very basic question.
I write my problem in pseudo code:

List<Employee> emps = Session.GetAll(); // select via Detached Criteria
emps[0].firstname += "1";
emps[1].firstname += "1";
emps[1].orders[0].shipname += "1";

session.begintransaction()
session.saveorupdate(emps[0]);
session.committransaction();

My intention in code is, to load all Employees, modifiy some data and only save the changes from the first employee.
But NHibernate makes three update Queries, even for the change in the order , where i set the cascade style to "none"

Can someone please explain whats going wrong ?

I think that the problem is that saveorupdate is not the method to save in db but simply to manage your entities in NHibernate session. In your case the call it is useless: the persistence is performed by committransaction that call a flush.

I think so, after days of attempts to address the same problem.

I hope that there is a solution.

exactly that is my problem.
Flush saves actualy to db and not saveorupdate.

But flush saves all changes made to objects loaded in the same session.
How can i prevent this behaviour /Save only the changes from one object ?

Nobody ?

I think this would help me to understand nhibernate a bit more

Alternative 1:
Try to evict objects that you dont want to save:

than save your item and attach "item_not_to_save" to your session again.
Its tricky could work, but anyway it is irritating with Hibernate. Image you have a list with 1000+ positions...
sesstion.save(item) and commit should only save "item" not all changes.wrrr... ;-)

Alternative 2:
Create second session "session2" and attach only object that are need to be saved, and save it in session2. Than retach them to your session1. Its tricky also...

Have found another way to do it.
Before saving call session.clear(), so after than only needed objects will be saved:



PS. Tested with NHibernate 3.1.0