Update problem

LasseL · **Joined:** Sun Mar 18, 2007 12:15 pm **Posts:** 19

Hi
I have a fairly complex business class, consisting of properties and collection (bags) nestet i a couple of levels. I've chosed use many ISessions according to chapter 10.4.2 in the manual.

Using one Session I fetches a instance of my business class from the database.
The application modifies this instance by changing property valus and adding/deleting items from the collection. Next step for the application is to save the changes to the database.

The application creates a new session and performs:session.SaveOrUpdate(item)
(there is a bit session and transaction manipulation first)

This immediatly generates a exception with the following message..

Quote:

Message = "deleted object would be re-saved by cascade (remove deleted object from associations): 51, of class: xxxxxx"

The referenced class xxxxx in of one of the collections.

Can anyone explain whats gone wrong, and what to do.
//lg

oalexandrino · **Posted:** Thu Aug 30, 2007 9:42 pm

I think my problem can be the same

http://forum.hibernate.org/viewtopic.php?t=979066

unhappily I dont know why

would you tell me if you found that solution please?
I could do the same

mnichols · **Joined:** Mon Aug 21, 2006 9:18 am **Posts:** 179

Please post mappings and code. You are either deleting an entity from a collection incorrectly or your mapping's cascade isn't set properly.

Mike

b3ardman · **Joined:** Tue Aug 15, 2006 11:01 am **Posts:** 10

[quote="mnichols"]Please post mappings and code. You are either deleting an entity from a collection incorrectly or your mapping's cascade isn't set properly.

Mike[/quote]

Yeah, you need to look out for the Cascade:AllDeleteOrphans

You might end up having your item deleted because it was removed from one association, but then recreated because it's still a member of another association.

If you can get rid of the M:N association, perhaps making it two 1:M associations, do that. It'll make like easier.

LasseL · **Joined:** Sun Mar 18, 2007 12:15 pm **Posts:** 19

mnichols wrote:

Please post mappings and code. You are either deleting an entity from a collection incorrectly or your mapping's cascade isn't set properly.

Mike

As I wrote, I've have a fairly complex application and .... posting the mappings.... well it will fill up quite a space....

To clearify. I have a business class "business" containing collections implemented by using List (list).

Removing a Entity from the List is done by :
business.list.RemoveAt[0]

The I excecute...:

session.SaveOrUpdate(business)

LasseL · **Joined:** Sun Mar 18, 2007 12:15 pm **Posts:** 19

b3ardman wrote:

mnichols wrote:

Please post mappings and code. You are either deleting an entity from a collection incorrectly or your mapping's cascade isn't set properly.

Mike

Yeah, you need to look out for the Cascade:AllDeleteOrphans

You might end up having your item deleted because it was removed from one association, but then recreated because it's still a member of another association.

If you can get rid of the M:N association, perhaps making it two 1:M associations, do that. It'll make like easier.

A matter of fact,,, I've implemented Many-To-Many relationships by using a middle class and One-To-Many and Many-To-One associations. My problems seems to be this middle class.