Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

'NHibernate.AssertionFailure: no collection snapshot for orphan delete' when saving an entity with an empty collection with delete-orphan cascade

Description

This bug is related to NHibernate 2.0 RC1, but I was not able to select this version.

The description of this bug was initially recorded as NHibernate Bug NH-1419; however, upon researching the problem it was determined to be occuring when using the NHibernate Mapping Attributes.

The attached project will recreate the error.

Environment

None

Attachments

1

Activity

Show:

Pierre Henri Kuaté October 22, 2009 at 3:48 PM

This is a NHibernate issue; nothing that NHMA can fix.

Former user March 2, 2009 at 4:07 AM

We need this issue to fixed for a threading-issue where we use 'refresh' for child-objects of a root-aggregate. In our case: orderlines is a bag within order, and we update orderlines on different threads. After that process we evict orderlines from the nhsession and than use refresh on the order.

The solution of using "save-update, delete, delete-orphan" instead of "all-delete-orphan" is described by Fabio Maulo in
http://groups.google.nl/group/nhibernate-development/browse_thread/thread/53aa292a0e451c4d?hl=nl&ie=UTF-8&q=cascading+matters++refresh#be15d28350ff487d

Can this issue be scheduled for a next release?

Dmitry Makarenko October 17, 2008 at 12:05 PM

Although it is fixed for "all-delete-orphan" it is still reproducible for
"save-update, delete, delete-orphan"

Brandon Kobel August 28, 2008 at 7:29 AM

This is not an issue with the NHibernate.Mapping.Attributes specifically.

The problem was with the cascade of "All-Delete-Orphan", it was suppsoed to be "all-delete-orphan".

External Issue

Details

Assignee

Reporter

Components

Affects versions

Priority

Who's Looking?

Open Who's Looking?

Created August 1, 2008 at 6:47 AM
Updated October 22, 2009 at 3:48 PM
Resolved October 22, 2009 at 3:48 PM
Who's Looking?