[Phpmyadmin-devel] mysql.host is obsolete
Looking at [1], our instructions to create a control user will no longer work beginning with MySQL 5.6.7. The MySQL documentation I've seen isn't clear on what this means (i.e. what we should do instead under the new versions), so does anyone have any suggestions? 1 - http://wiki.phpmyadmin.net/wiki/index.php?title=Talk:control_user&curid=1786...
Isaac Bennetch a écrit :
Looking at [1], our instructions to create a control user will no longer work beginning with MySQL 5.6.7. The MySQL documentation I've seen isn't clear on what this means (i.e. what we should do instead under the new versions), so does anyone have any suggestions?
1 - http://wiki.phpmyadmin.net/wiki/index.php?title=Talk:control_user&curid=1786...
Thanks Isaac for alerting us about this. I'll study more about this, but my first reaction is that we might be able to change the doc, to indicate that the control user only has one goal: to connect to the phpMyAdmin configuration storage. By the way, in [2] we decided to move the user doc away from the wiki. [2] http://wiki.phpmyadmin.net/pma/DebConf_2013_Team_Meeting#Teams
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-- Marc Delisle http://infomarc.info | http://phpmyadmin.net
Hi Dne Fri, 21 Feb 2014 09:36:45 -0500 Isaac Bennetch <bennetch@gmail.com> napsal(a):
Looking at [1], our instructions to create a control user will no longer work beginning with MySQL 5.6.7. The MySQL documentation I've seen isn't clear on what this means (i.e. what we should do instead under the new versions), so does anyone have any suggestions?
Do we really need those privileges on mysql.* tables? Looking at the code I can't find any obvious use for that. -- Michal Čihař | http://cihar.com | http://phpmyadmin.net
Michal Čihař a écrit :
Hi
Dne Fri, 21 Feb 2014 09:36:45 -0500 Isaac Bennetch <bennetch@gmail.com> napsal(a):
Looking at [1], our instructions to create a control user will no longer work beginning with MySQL 5.6.7. The MySQL documentation I've seen isn't clear on what this means (i.e. what we should do instead under the new versions), so does anyone have any suggestions?
Do we really need those privileges on mysql.* tables? Looking at the code I can't find any obvious use for that.
There was/is the issue of supporting servers running with --skip-show-database, and maybe another issue. I have to do some more research about this today. -- Marc Delisle http://infomarc.info | http://phpmyadmin.net
Le 2014-02-24 08:34, Marc Delisle a écrit :
Michal Čihař a écrit :
Hi
Dne Fri, 21 Feb 2014 09:36:45 -0500 Isaac Bennetch <bennetch@gmail.com> napsal(a):
Looking at [1], our instructions to create a control user will no longer work beginning with MySQL 5.6.7. The MySQL documentation I've seen isn't clear on what this means (i.e. what we should do instead under the new versions), so does anyone have any suggestions?
Do we really need those privileges on mysql.* tables? Looking at the code I can't find any obvious use for that.
There was/is the issue of supporting servers running with --skip-show-database, and maybe another issue. I have to do some more research about this today.
I could not find any other reason than supporting servers running with --skip-show-database. -- Marc Delisle http://infomarc.info | http://phpmyadmin.net
Hi Dne Mon, 24 Feb 2014 15:31:26 -0500 Marc Delisle <marc@infomarc.info> napsal(a):
I could not find any other reason than supporting servers running with --skip-show-database.
I know this is documented, but do we actually use this? I've just tried to run MySQL with this option and phpMyAdmin works just fine without controluser. Looking at the code, I've only found it in List_Database.class.php and this code is never executed as the query against information schema works even with --skip-show-database. So I suggest to remove this code: https://github.com/phpmyadmin/phpmyadmin/pull/963 Also as we no longer use SHOW DATABASE, related section of docs can be IMHO removed: https://github.com/phpmyadmin/phpmyadmin/pull/964 -- Michal Čihař | http://cihar.com | http://phpmyadmin.net
Le 2014-02-26 03:06, Michal Čihař a écrit :
Hi
Dne Mon, 24 Feb 2014 15:31:26 -0500 Marc Delisle <marc@infomarc.info> napsal(a):
I could not find any other reason than supporting servers running with --skip-show-database.
I know this is documented, but do we actually use this? I've just tried to run MySQL with this option and phpMyAdmin works just fine without controluser.
Looking at the code, I've only found it in List_Database.class.php and this code is never executed as the query against information schema works even with --skip-show-database. So I suggest to remove this code:
https://github.com/phpmyadmin/phpmyadmin/pull/963
Also as we no longer use SHOW DATABASE, related section of docs can be IMHO removed:
We have at least one bug report active, from a user who has poor performance with a huge number of databases / tables. He suggests to reinstate the SHOW DATABASES logic. -- Marc Delisle http://infomarc.info | http://phpmyadmin.net
Hi Dne Wed, 26 Feb 2014 05:37:23 -0500 Marc Delisle <marc@infomarc.info> napsal(a):
We have at least one bug report active, from a user who has poor performance with a huge number of databases / tables. He suggests to reinstate the SHOW DATABASES logic.
I guess you mean bug #4243 [1]. In this case, I'd rather use the UNION select he suggests than going back to the SHOW DATABASES... [1]: https://sourceforge.net/p/phpmyadmin/bugs/4243/ -- Michal Čihař | http://cihar.com | http://blog.cihar.com
Michal Čihař a écrit :
Hi
Dne Wed, 26 Feb 2014 05:37:23 -0500 Marc Delisle <marc@infomarc.info> napsal(a):
We have at least one bug report active, from a user who has poor performance with a huge number of databases / tables. He suggests to reinstate the SHOW DATABASES logic.
I guess you mean bug #4243 [1]. In this case, I'd rather use the UNION select he suggests than going back to the SHOW DATABASES...
Agreed for this case, so feel free to merge your pull requests. In the long term, I expect that all performance problems of information_schema will disappear (or at least that SHOW DATABASES is not faster...). In bug #4243 the user is running MySQL 5.5. The last feedback I got from the admin of db4free.net is that he could not trigger information_schema performance problems, but he was running MySQL 5.6. -- Marc Delisle http://infomarc.info | http://phpmyadmin.net
Hi Dne Thu, 27 Feb 2014 08:20:16 -0500 Marc Delisle <marc@infomarc.info> napsal(a):
Agreed for this case, so feel free to merge your pull requests.
Okay, will do so.
In the long term, I expect that all performance problems of information_schema will disappear (or at least that SHOW DATABASES is not faster...).
Hopefully, but it takes incredibly long.
In bug #4243 the user is running MySQL 5.5. The last feedback I got from the admin of db4free.net is that he could not trigger information_schema performance problems, but he was running MySQL 5.6.
That's good news. -- Michal Čihař | http://cihar.com | http://blog.cihar.com
participants (3)
-
Isaac Bennetch -
Marc Delisle -
Michal Čihař