Hii everyone, I have submitted a proposal for the GSoC project 'Support for Procedures' on the GSoC site. Please provide me with your valuable feedback and suggestions.
Regards, Atul
I have also submitted my proposal 'Query statistics & charts for the status page' on the GSoC site 2 days ago and would be very thankful if a mentor could look over it before the end of the submission time.
Thanks in advance, Tyron
On Sun, Apr 3, 2011 at 8:13 PM, Atul Pratap Singh atulpratapsingh05@gmail.com wrote:
Hii everyone, I have submitted a proposal for the GSoC project 'Support for Procedures' on the GSoC site. Please provide me with your valuable feedback and suggestions.
Regards, Atul
-- Atul Pratap Singh III yr Undergraduate Student Institute Of Technology, Banaras Hindu University, Varanasi, India.
Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Tue, 5 Apr 2011 14:08:17 +0200 Tyron Madlener tyronx@gmail.com napsal(a):
I have also submitted my proposal 'Query statistics & charts for the status page' on the GSoC site 2 days ago and would be very thankful if a mentor could look over it before the end of the submission time.
Basically I don't have other comments that which I've already posted on this mailing list. Generally it might be useful addition, but requires some amount of configuration, what is something our users tend to avoid doing. So it might end up being another hidden feature nobody knows.
Thanks for the reply! I don't think there is any configuration required other than clicking a button to enable the slow_query_log and disabling it again at a later point. I would let the code configure the slow_query_log once the user decides to enable logging.
As for the sever status recording, if it would be using the database to keep the history, it could also just be set up with a click of a button using a default configuration. It could still allow configuration through the config.php or within a dialog, but only if the user desires so. Maybe I should add that to my proposal.
What other configuration would it require?
On Tue, Apr 5, 2011 at 2:34 PM, Michal Čihař michal@cihar.com wrote:
Hi
Dne Tue, 5 Apr 2011 14:08:17 +0200 Tyron Madlener tyronx@gmail.com napsal(a):
I have also submitted my proposal 'Query statistics & charts for the status page' on the GSoC site 2 days ago and would be very thankful if a mentor could look over it before the end of the submission time.
Basically I don't have other comments that which I've already posted on this mailing list. Generally it might be useful addition, but requires some amount of configuration, what is something our users tend to avoid doing. So it might end up being another hidden feature nobody knows.
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
Hi
Dne Tue, 5 Apr 2011 14:51:57 +0200 Tyron Madlener tyronx@gmail.com napsal(a):
Thanks for the reply! I don't think there is any configuration required other than clicking a button to enable the slow_query_log and disabling it again at a later point. I would let the code configure the slow_query_log once the user decides to enable logging.
Indeed, for superuser this can be configured at runtime. Unfortunately most of our users do not have such privileges.
As for the sever status recording, if it would be using the database to keep the history, it could also just be set up with a click of a button using a default configuration. It could still allow configuration through the config.php or within a dialog, but only if the user desires so. Maybe I should add that to my proposal.
Probably same as for other parts of phpMyAdmin configuration storage would apply here. What means nobody sets up the required infrastructure on shared hosting.
-
Atul Pratap Singh -
Michal Čihař -
Tyron Madlener