I think this is asked very frequently (including by me, just a couple weeks
ago), and very little reply, but it's safe to say that it's still unsuported
till date, and possibly will never be.
Currently the workaround I use has always been mapping to a one-to-many
private list field, and have your setter/getter to access the first item in
that list.
I.e.
private readonly IList<Something> list = new List<Something>();
public Something Property{
get{return list.First();}
set{list.Clear(); if(value != null) list.Add(value);}
}
Then map that "list" field in the hbm using one-to-many
On Tue, Nov 23, 2010 at 4:02 AM, gusgorman <[email protected]>wrote:
> Hi,
>
> Was cascade="all,delete-orphan" ever implemented in Nhibernate?
>
> It certainly wasn't at one point (see
>
> http://colinjack.blogspot.com/2008/03/nhibernate-gotchas-orphans-and-one-to.html
> ).
>
> many thanks,
> Jordan.
>
> --
> You received this message because you are subscribed to the Google Groups
> "nhusers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<nhusers%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
