When entering a database where the configuration storage tables are not present, phpMyAdmin offers to create them from the Operations tab.
Doesn't appear to be right if you indeed only support one set of PMA tables.
If the tables are shared with multiple DBs I do NOT want them to be in one of the DBs.
I think you should reconsider.
What is the recommended way to export / import the relations of ONE specific DB?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The proper way of setting up the configuration storage is via config.inc.php. This way, you can indicate exactly where you want the storage to be. The ZeroConf mechanism is a way to help those who don't want to properly configure, and IMO cannot support all possible scenarios.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
IMO you should try to create the tables in a separate DB (phpmyadmin) and only if that fails offer the user the option to create them in the current DB.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Olaf,
IMO, this becomes an issue for you, only because you choose to not do the recommended configuration. As the team decided to not support per-db configuration storage, I am closing this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
IMO having pMA tables in every database is not the right approach to export metadata such as relations when exporting structure and/or data.
We probably can offer users an option in the export page to export such metadata.
Can you please raise a feature request for such a feature.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Olaf,
after looking at the impact of duplicating the configuration storage in all the databases, we decided to support the scenarios which are explained in
http://docs.phpmyadmin.net/en/latest/setup.html#phpmyadmin-configuration-storage
That sucks :p
Covered?
Doesn't appear to be right if you indeed only support one set of PMA tables.
If the tables are shared with multiple DBs I do NOT want them to be in one of the DBs.
I think you should reconsider.
What is the recommended way to export / import the relations of ONE specific DB?
Typo fixed in the repo.
The proper way of setting up the configuration storage is via config.inc.php. This way, you can indicate exactly where you want the storage to be. The ZeroConf mechanism is a way to help those who don't want to properly configure, and IMO cannot support all possible scenarios.
Right, but then how do I export and import relations and other stuff of just a single DB?
IMO you should try to create the tables in a separate DB (phpmyadmin) and only if that fails offer the user the option to create them in the current DB.
Scheduled to be discussed at the next team meeting:
https://wiki.phpmyadmin.net/pma/2015-02_Meeting
Exporting and importing wasn't discussed at the meeting right? IMO that's THE issue.
Olaf,
IMO, this becomes an issue for you, only because you choose to not do the recommended configuration. As the team decided to not support per-db configuration storage, I am closing this.
Not supporting per-DB storage is (kinda) fine, but the issue of per-DB export/import of this data isn't addressed yet.
Could you give an example of what you mean by "What is the recommended way to export / import the relations of ONE specific DB?"
What kind of relations?
Relations between fields (foreign keys) and other (per-DB) data stored in the pMA storage.
Ok, but in your case, these are normal tables in your db, correct? So when you export, these tables are not present in the exported result?
They might be in the same DB, they might be somewhere else, both when exporting and when importing.
AFAIK when exporting a database pMA does not export the pMA data if it's stored in a separate DB.
IMO having pMA tables in every database is not the right approach to export metadata such as relations when exporting structure and/or data.
We probably can offer users an option in the export page to export such metadata.
Can you please raise a feature request for such a feature.