Hibernate version: 1.2.0.GA

I am trying to delete an entity which is in a child collection of another entity. For example, I am trying to delete a ContactAddress entity, which is a member of a Contact entity's Addresses collection.

I do this:



This executes OK, but when the session is flushed, I get a SQL error about NHibernate trying to update the contact address row with a null value for the contact ID foreign key column. Buty since I called ISession.Delete() on myContactAddress, it shouldn't consider it for updating (or re-inserting) even if it appears "dirty". Doesn't it know it's marked as deleted? This sounds like a bug to me ...

We really don't want to disable the automatic maintenance of parent property values in our collections when items are added and removed, so it isn't an option on our end to try working around it by preventing the entity being deleted from getting "dirty". (If we don't remove it from the parent's collection, we get an exception that the deleted entity would be resaved by an update ...)

Since we track our own deleted status (and dirty status) on our entities, I was able to work around it by implementing IInterceptor.FindDirty like this:

NHibernate considers collection updates separately from updates to contained objects, this may be why you see this problem occurring. You should be able to prevent it using inverse="true" for the Addresses collection.

All of our collections are already mapped as inverse=true. They are all mapped as bags.

Hi. I have the same problem. The difference is I have 2 bags point to same entity, like a many to many. I didn't use many-to-many because the entity reserve has more fields besides the keys.

Client [bag]-> reserve <-[bag] Item

I tried to use inverse in both sides and no inverse too. In all cases NHibernate tries to update one of the keys in reserve with null value and fails.

The only way I made it work was mapping both bags with inverse and delete de reserve myself. I don't know if it is the better choice.