Hello,

I'm having trouble making any changes to my many-to-many collection. I get a "object already associated with session" message but nothing happens when I do Update() ... I also tried Save() and SaveOrUpdate() but it doensn't want to do it.
When I make changes to my joining table directly in the database I can see that the collections are correctly populated ... so reading works, I just can't get it to write. This is my code:

Mapping file:


File.cs


Keyword.cs


Client code


Log



I'm out of ideas about what could be wrong.. I realize that calling the update on the class that has inverse=true will result in no update, but I'm calling both here (and one of them is inverse=false) so why is it not doing the update? I also tried doing lazy=false but that didn't help much either. I originally copied this code from one sample - it didn't have a setter method on the Keywords and Files properties but instead a new ArrayList() initialization of the private variable ... but having it like that was no better than the way I have it now.

What am I missing here?

Thank you,
Tomas

i am pretty sure you don't want to have "cascade="none"" in there. that is telling hibernate to ignore any statements (update, save, delete, etc). try setting cascace="save-update"

-devon

Thanks, before I had cascade="all" and that didnt' work ... and unfortunately "save-update" didnt' work either. I get the same notification. Any other ideas?

Thanks,
Tomas

I finally figured it out ... I was missing transaction.commit ... I would like to say that I forgot but in reality I had it like this on purpose. I have written one simple application in 0.7 and none of my saves had transactions around them and it works just fine. That's why got in the bad habit of not using them.

So how does it work? I started to think that transactions are optional and used only if you want to have the choice of rolling back. (that even if I don't use transactions changes will be written when I call session.Close())

But in this case it doesn't seem to be so.... was there a change between 0.7 and 0.8.4?

Thank you!
Tomas

Transaction are optional. But, transaction.commit inherintly does a Session.Flush(). So, if you don't use transactions you have to Flush. There are some times when flush happens automatically though.

I don't think this has changed since .7.

BOb

Calling Update doesn't do anything at all for persistent objects. Save/Update/Delete only record the needed changes in the session, and Flush executes them.

Inserts do happen during Save if you use the "identity" id generator, because NHibernate has to return the identifier of the new object and it's not possible to do without actually inserting the object.

Ok that explains it ... thank you

Tomas