Hi Carlos, no there is not. As far as I know there is no such mechanism that removes the elements from initialized collections. This can depending on your cascade settings even result in a resave of deleted objects.
On Jul 13, 3:00 pm, Carlos cubas <[email protected]> wrote: > This is a question in regard to a blog post by Fabio on executable > queries.http://fabiomaulo.blogspot.com/2009/05/nhibernate-210-executable-quer... > > Taking the example from his post how do executable queries, the > session cache and the 2nd level cache interact? > > In the case of: > DELETE FROM Animal a WHERE a.BodyWeight = 200 > > What happens with animals already loaded in the session cache. Is this > equivalent to > > select id from Animal a where a.BodyWeight = 200 > delete from Animal a where a.BodyWeight = 200 > //remove from session cache by ids > > What happens with animals already associated in a collection. > Something like (zoo 1:n animal) > Is there some internal mechanism that will synchronize the > collections? > > Zoo.Animals.Count = 400 > delete from Animal a where a.BodyWeight = 200 --deletes 3 animals > Zoo.Animals.Count = ? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
