hi
Page 257:
“The user's location is not retrieved directly from her profile in the preceding code because that would cause a read for each and every row. Insteaad, the user's country, state, and city are read only once from the profile and saved in local variables.”

a) Profile for current user is retrieved from the DB the first time Profile object is accessed, but from that point onward, you can read it without any DB work. So I don’t see how process time is saved if we save user’s location in local variables?!

thanx

Where are you getting this information? To my knowledge, the ASP.NET runtime does not cache the Profile data.

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

It’s from book Pro Asp.Net 3.5 iin C# 2008.:
“The first time you access Profile object in your code, Asp.Net retrieves the complete profile data for current user from the DB. From this point onward, you can read the profile information in your code without any further database work(until the next postback)”


Anyways, I didn’t say Asp.Net saves profile data for current user across postbacks, but it does save it during the processing of the current request, while author implies that even during the processing of the current request the profile data for current user is retrieved every time we access Profile property

Who's book is that?

I still don't think that's correct. As far as I know, profile properties are retrieved one at a time as they are called.

This is actually MORE efficient that retrieving the entire Profile object in most cases.

Maybe that author is misinformed. Or maybe I am, but I don't think so.

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

hi

It’s by Mathew MacDonald.


You mean that particular profile property for current user is retrieved from DB each time it is called, OR just once ( and then it is saved for the duration of current request )?

But even if individual profile property for current user are retrieved the first time it is called ( and then it's saved for the duration of the current request ), then author is still wrong, since calling user’s location directly from profile for each and every row wouldn’t have cause “read ( from DB ) for each and every row” and thus we don’t save any process time if we save user’s location in local variables

cheers mate

No, what I am saying is that the data is retrieved from the DB each time a property is accessed. There is no mechanism that I'm aware of that saves it as part of the current request. This means that if you are accessing the data repeatedly (as part of a loop for example), a fetch to the DB takes place for each pass.

This is because the ProfileCommon class fetches property values by calling the GetPropertyValue method, and then casting to the type of the property. The GetPropertyValue method invokes the aspnet_Profile_GetProperties stored procedure in the database.

Also, the ProfileCommon class does not cache the values as they are retrieved.

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

I apologize for not replying sooner, but my PC was in repair

Anyways, thanx for helping me out

cheers