Quote:
Originally Posted by KirbyDE
How does the Datastore Class (on subsequent Pageloads) know that there are no Entries that need to be cached, and thus does not execute the Query?
How does it know which entries need to be made available as $vbulletin->name?
|
Looking at the code, there is no precaching features in the other data methods. (The query i posted above predicts what is needed via the new table, and the datasore item does not need to be added to $specialtemplates because of the conditions).
It will indeed make another call to the other datastore storage, but as i understand it (and i could be wrong), for memcached it will query the storage each time it needs an item regardless of if it is stored in the proper storage method and if it isnt, it will query the datastore table and add it to cache.
For file based, as far as i understand, the entire datastore is loaded into memory. I could be very wrong in this assumption and there may need to be file changes to both datastore classes to make it work properly. It may turn out that for other datastore methods (if we go with the table solution) there needs to be an additional query to the NEWTABLE table.
Im not 100% sure that it will work for them, because I dont really know the mechanics. Ill look into it furthur if I have time today.