-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
2015 02_Meeting
See also the 2015-02 Meeting IRC Log
Should we change how it works? See
--Lem9 13:45, 9 February 2015 (CET)
We have decided to not implement per-database Configuration Storage settings; this should be global across a user's access so as to not introduce duplicating or missing data.
However, we will change the existing behavior so that, with ZeroConf set to true, phpMyAdmin will first try to use the current database, then a `phpmyadmin` database and offer to create it.
The reason the current database will be tried before `phpmyadmin` is because we're expecting this to mostly be used by shared-hosting users where they have access to only one database; users who have full control will properly configure their config.inc.php manually and this is the most efficient way to serve the shared hosting users effectively.
The change will target the 4.4 release.
Let's discuss https://sourceforge.net/p/phpmyadmin/bugs/4752/
--Lem9 18:17, 9 February 2015 (CET)
After discussion where we fully realize that we won't be able to serve the desires of all users simultaneously, it was decided to take the user to the table structure page. Additionally, the behavior will be changed when creating a database to go to the database structure page. See also https://sourceforge.net/p/phpmyadmin/bugs/4761/
This list has been gathered by Madhura for discussion:
--Lem9 08:26, 10 February 2015 (CET)
This was quite a productive part of the meeting.
Regarding 260, we feel this is too fragile to implement for the same reasons we removed editing rows that do not have a primary key. For 406, this is really not ideal use of the relational features and probably best left not implemented.
Popular destinations:
- Team meetings
- GSoC home
- Developer guidelines
- How to install on Debian and Ubuntu
- Issue and pull-request management
User resources: