MySQL Table Prefix Changer Tool in PHP - Putting the database back together
(Page 4 of 4 )
At this point in execution we are left with an array full of table names that have been reconstructed using the new table prefix. Now we need to write that information back to our database.
// Write new table names back
foreach ($table_array as $key => $value) {
$query = sprintf('RENAME TABLE %s TO %s', $table_array[$key], $table_names
[$key]);
$result = mysql_query($query, $link);
if (!$result) {
$error = mysql_error();
echo "Could not $query : $error<br>";
} else {
$message = sprintf('Successfully renamed %s to %s in %s', $table_array
[$key], $table_names[$key], $mysql_db);
echo "$message<br>";
}
}
To do that, we will use a Foreach loop to iterate through each of our array elements. Then it’s just a matter of forming a query that renames the table. Now you can see why we created a duplicate array with our new table names instead of simply editing the existing one.
We have two side-by-side arrays: one with old names and one with new, in the same order. By moving through each of them at the same time we can get the old and new table names without ever having to know how many tables we’re even working with.
// Free the resources
mysql_close($link);
}
All of the dirty work is done. All that’s left is to close our database connection and create the replace_prefix() function that actually determines the new table names for us.
function replace_prefix($s, $prefix) {
$pos = strpos($s, "_");
$s = substr($s, $pos + 1);
$s = sprintf("%s_%s", $prefix, $s);
return $s;
}
?>
Our custom replace_prefix() function is actually pretty simple. It accepts two parameters: the original table name and the new prefix. A few simple string functions parse out the old prefix and replace it with the new.
Voilà! We’re all done. Save this with a .php extension and upload it to your web server. Access your script in your web browser to see it in action. Do not forget to update your site’s configuration settings with the new table prefix information BEFORE running this script; otherwise, you may not be able to access it afterward.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 13 
