Hello,

Sorry for having two active topics, but the following is driving me nuts:

Author said Article.Body property uses lazy load pattern, where Body field is retrieved only when Body property is accessed for the first time. I understand the concept of lazy load pattern, but for this pattern to work, certain stored procedures (which according to author (page 222) don’t retrieve Body field) shouldn’t retrieve Body field, but they do.

Is this just a typo and thus we can correct it by simply changing SELECT query ( in a stored procedure) to not retrieve Body field, or would other changes also be necessary for lazy load pattern to work with Body property?

thanx

You are correct in noting that the lazy-load implementation is flawed.

This is because while the implementation does prevent the body of an article from being loaded into article lists, it does not prevent the body from being retrieved from the database, loaded into the reader, and carried across the wire, which is where the real performance bottleneck lies.

To correct this, you could simply prevent the body from being retrieved in any sproc that returns multiple articles. This might involve changing the application code in some places as well.

__________________
Visit my blog at http://leedumond.com
Follow me on Twitter: http://twitter.com/LeeDumond

Uhm, are you sure about also needing to change some of application code? I thought preventing procedures from retrieving Body would suffice?


thanx

Absolutely not sure.

I said you "might" have to, but I haven't really traced through the code closely enough to know. I'd say the best way to be sure is to try it.

__________________
Visit my blog at http://leedumond.com
Follow me on Twitter: http://twitter.com/LeeDumond

thanx for helping me out

cheers

My thought is that you would have to change the following stored procedures:
tbh_Articles_GetArticles, tbh_Articles_GetArticlesByCategory, tbh_Articles_GetPublishedArticles, tbh_Articles_GetPublishedArticlesByCategory.

At the same time there would be no purpose in overloading the GetArticleCollectionFromReader method in the ArticlesProvider class and call the GetArticleFromReader method using false as the second parameter.

However, even though it is true that the implementation does not really avoid retrieving the bodies from the database, it allows for article lists to have the body. I assume this could be useful if you want to implement a news section where you would need to edit several articles at the same time. Of course you could create specific stored procedures for those cases, and use the ones without the bodies for article listing purposes.