> It's the hidden price of Lazy loading (or load on demand) which > is definitely not obvious when you walk through a set of > properties.
It's hidden, but not entirely new work, since without the lazy load, you end up including all those columns in the initial searching query. That sometimes gives the SQL database fits because it chooses the wrong query plan in the face of so many joins. Additionally, you gain something for every lazy FK that isn't derefed, and you gain something for every search match that doesn't get derefed. In customer-facing systems that hold huge amounts of largely static data, often only the first row of a search is ever used. Marc =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
