nettika/phpmyadmin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

unwanted side effect of tracking when renaming a database

Browse Source
This commit is contained in:
Marc Delisle
2010-01-01 22:57:34 +00:00
parent d3892fdbff
commit f92038b022
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
db_operations.php
View File

@@ -53,7 +53,13 @@ if (strlen($db) && (! empty($db_rename) || ! empty($db_copy))) {
} }
$local_query .= ';'; $local_query .= ';';
$sql_query = $local_query; $sql_query = $local_query;
// save the original db name because Tracker.class.php which
// may be called under PMA_DBI_query() changes $GLOBALS['db']
// for some statements, one of which being CREATE DATABASE
$original_db = $db;
PMA_DBI_query($local_query); PMA_DBI_query($local_query);
$db = $original_db;
unset($original_db);
// rebuild the database list because PMA_Table::moveCopy // rebuild the database list because PMA_Table::moveCopy
// checks in this list if the target db exists // checks in this list if the target db exists