ley us see the implementation of the collection getter On Tue, Jun 1, 2010 at 10:37 AM, sternr <[email protected]> wrote:
> Hi, > (I hope I'm posting in the right news-group, if not please refer me in > the right direction, thanks!) > > I'm developing an ASP.Net web application using NHibernate, in a > session-per-request paradigm. > I've got a page, where the user can update a certain entitiy. > My Code-Behind creates a new entity with the form's data and calls the > Session.SaveOrUpdateCopy method to do the actual update. > > This works perfectly well, except for a certain entity I have, which > has a collection of a different entity mapped with cascade all. (a > simple one-to-many with cascade all). > > The problem is, since the update page allows updating only the flat > entity properties, the collection stays null, and the update process > deletes all the related childs (because of the cascading). > The thing is, I need the cascading option as specified (for other > scenarios, like delete a child entity etc.). > > Is there a way to tell NHibernate not to update this "undirty" > properties? > Thanks! > > --sternr > > -- > 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. > > -- Fabio Maulo -- 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.
