If I remember correctly, nh 1.2 never cascaded when refreshing. In >=2.0 there is a cascade setting, "refresh", deciding this (if you have all/all-delete-orphan, refresh is included).
Whether you use lazy loading or not, I think doesn't matter. ________________________________________ Från: [email protected] [[email protected]] för joe [[email protected]] Skickat: den 15 januari 2009 18:45 Till: nhusers Ämne: [nhusers] ISessionManager.Refresh in 2.0.1 GA issue Has anyone run into an issue in NH 2.0.1 GA? I've upgraded recently from 1.2, and have noticed that is the ISessionManager.Refresh() is called for an object already loaded in the session, that a cascade forces loading of all child objects, even if the map specifies that they are lazy. The first call to Refresh() does not do this, just the subsequent calls. Is there a ticket already out there, or has anyone seen this? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
