looks like you have to separate domains: 1. business domain where business processing stuff happen, and lazy loading is needed 2. fetching domain, when a part of the object graph should be loaded completely and serialized to a remote location
so, you can have two separate mappings, one for each. On Thu, Feb 5, 2009 at 3:16 PM, Stefan Steinegger <[email protected]>wrote: > > I have the problem that I would like to turn off lazy loading at all > for certain queries. Most of our data is requested by the client > (WCF), and needs to be complete. > > I know a can turn of lazy loading in the query. But to do this, I have > to declare all the references an entity has. Many objects are simply > loaded using "Get(id)" or by a general, simple criteria which filters > by a business id. Turning off lazy loading for all referenced object > would result in much more queries which will be complicated and hard > to maintain. > > So I turned it off in the mapping files. Now it's hard to get lazy > loading back. I need something like "session.Lazy(false)" or > "query.Lazy(false)" or something. If something like this would exist > somewhere, I didn't find it. > > > -- Ken Egozi. http://www.kenegozi.com/blog http://www.delver.com http://www.musicglue.com http://www.castleproject.org http://www.gotfriends.co.il --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
