#746 Group databases with the same structure
Most developers have several databases with the same structure, f.e. one on the development server & one on the production server.
Unfortunately they have to tune phpMyAdmin for every DB separately. It's very annoying because databases are often complex & their tuning in PMA takes a lot of time.
The idea is to support "database groups", with DBs processed by PMA in the same way.
For example, if I have databases `db_test` & `db_work`, I write to config.inc.php:
$cfg['Servers'][$i]['pmadb_groups']['db_work'] = 'db_test';
.. and `pmadb` settings for both databases are stored in one place with 'db_test' database name.
In particular this works if `db_test` & `db_work` are on different servers & `db_work` is managed on development machine through SSH.
If 3 tables have the same structure, config would be like
$cfg['Servers'][$i]['pmadb_groups']['db_work_1'] = 'db_test';
$cfg['Servers'][$i]['pmadb_groups']['db_work_2'] = 'db_test';
.., etc. I add the patch for phpMyAdmin-3.5.0, saved by Tortoise SVN. All works fine.
Patch for phpMyAdmin-3.5.0, saved by Tortoise SVN.
I think that you could just use the synchronisation feature that is already available to keep different databases up to date with each other.
The task this request solves is not to synchronize databases' content, but having several databases with different content but same structure (f.e. development & production databases), tune them in PMA as single unit. PMA has many nice features like transformation, but currently they must be configured for each database separately.
In version 3.5.0, "phpMyAdmin configuration storage" database contains 12 tables.
In my patch, when databases are in the same group (like `db_test` & `db_work` in request Details), they share settings in pma_bookmark, pma_column_info, pma_designer_coords, pma_pdf_pages, pma_relation, pma_table_coords, pma_table_info & pma_table_uiprefs (8 tables).
They DON'T share settings in pma_history, pma_recent & pma_tracking (3 tables).
Table pma_userconfig stores no database data (1 table).
The patch won't correctly support relations between different databases (own pma's, not MySQL feature). Such relations must be processed with DBs' real names, not with container-groups' names. I don't use pma-relations between databases so it's no problem to me.
Moved to Patches.
Can be created & published database settings for popular CMSs like Joomla! etc., so developer will be able to download & import into his pmadb database f.e. joomla_2.5.sql.gz, and include his Joomla DB into "joomla_2.5" group.