Cache System Explanation (datastore)
by
17 Mar 2006
I'm going to try and explain the datastore system used in vBulltin. This tutorial is based around users who are already familar with PHP and MySQL. What is Cache? I'll show you way using the datastore is a better solution for you and the users who will use your hacks. &d=1142583798" rel="Lightbox_927398" id="attachment44423 Now everytime you add, edit, or delete your information, it will be changed in the database. Here is an example of the database tree. We have 3 rows of information. &d=1142583798" rel="Lightbox_927398" id="attachment44424 PHP Code:
$query = $vbulletin->db->query_read("
Then you need to use the function called build_datastore(). This function requires the following. build_datastore(1, 2). #1 is the name of your datastore item, and number two is the http://us2.php.net/manual/nl/function.serialize.php information to store. This function will create a new datastore item with the name and all your info. The serialize info will look like this... Code:
a:3:{i:0;a:3:{s:2:"id";s:1:"1";s:4:"name";s:3:"Dog";s:5:"value";s:3:"Dog";}i:1;a:3:{s:2:"id";s:1:"2";s:4:"name";s:3:"Cat";s:5:"value";s:3:"Cat";}i:2;a:3:{s:2:"id";s:1:"3";s:4:"name";s:3:"Cow";s:5:"value";s:3:"Cow";}} &d=1142583798" rel="Lightbox_927398" id="attachment44425 Don't let the serialize data freak you out. You don't really NEED to read that data. Though I kinda like doing it, so I'll break it down alittle for you. Here is a tree of the serialize data. Code:
a:3:{ i:0; a:3:{ s:2:"id";s:1:"1"; s:4:"name";s:3:"Dog"; s:5:"value";s:3:"Dog"; } i:1; a:3:{ s:2:"id";s:1:"2"; s:4:"name";s:3:"Cat"; s:5:"value";s:3:"Cat"; } i:2; a:3:{ s:2:"id";s:1:"3"; s:4:"name";s:3:"Cow"; s:5:"value";s:3:"Cow"; } } PHP Code:
$data = array(
PHP Code:
$vbulletin->dropmenu = unserialize($vbulletin->dropmenu);
(ID: 1) (Title: Dog) (Value: Dog) (ID: 2) (Title: Cat) (Value: Cat) (ID: 3) (Title: Cow) (Value: Cow) What your doing is simple. The variable $vbulletin->dropmenu holds the information though it's still serialize. The reason why $vbulletin->dropmenu is the variable is because you need to tell vBulletin which datastore row to get. In this case it is dropmenu because remember we stored it in there like this: build_datastore('dropmenu', serialize($variable_array)); Now in order for vBulletin to know about that specific row, you need to add it to the $specialtemplates array. Example: PHP Code:
$specialtemplates = array(
So $vbulletin->dropmenu = unserialize($vbulletin->dropmenu); baiscly gets the serialize info and unserialize's it using the function called http://us2.php.net/manual/nl/function.unserialize.php Once that is finished you want to loop the info using a http://us2.php.net/manual/nl/control-structures.foreach.php function. foreach ($vbulletin->dropmenu AS $dropmenu). Doing that is storing the array info into $dropmenu and you can get each one by using the following vaiables. $dropmenu['id'], $dropmenu['title'], and $dropmenu['value']. The reason why this is better is because vBulletin allready runs one global query to get all the datatore information. So instead of running a query everytime you want to get the drop down information, you just get it from the datastore and save that query. Some may think this is kinda extreme when you can just run a query, though as your site grows; you want to save as many queires as possiable. If your interested in saving queries and bandwidth. I would suggest taking a look at Trigunflames profile. He has released many hacks to help in these areas. Copyright ©2004-2006 http://www.vbhackers.com All Rights Reserved. This tutorial may not be redistributed in whole or significant part. |
Similar Mods
Board Optimization datastore cache to XCache - boost your vBulletin | vBulletin 3.6 Add-ons |
Cache the datastore in the filesystem | vBulletin 3.0 Beta Releases |