I would like to contribute to phpmyadmin.
I have used it (phpmyadmin) frequently and i am good at php as well as
MySql (and also web-dev stuff like JS,html etc). Apart from that i also
worked with Indian Government to check out the government applications for
security vulnerabilities and audited them. Also as part of my open source
contribution i found a script injection vulnerability (XSS) in apache
openmeetings https://issues.apache.org/jira/browse/OPENMEETINGS-793 .
Please let me know if there is anything i can help in to contribute to this
Bits Pilani KK Birla Goa Campus
Computer Science Department
This is a follow-up to the "Minimum MySQL version thread".
I have worked on these bugs   and could not reproduce the problem.
However I believe the reports.
Considering that MySQL 5.5 has reached the "Generally Available" status
on 2010-12-03 with version 5.5.8, I think we should declare this version
as the minimum one for phpMyAdmin 4.1.0.
As suggested previously, we could drop the DisableIS and
ShowDatabaseCommands directives, and switch to INFORMATION_SCHEMA
everywhere we tested DisableIS or we used SHOW DATABASES.
I would really appreciate replies on this one.
For the upcoming phpMyAdmin 4.1, we currently advertise the minimum
MySQL version to 5 (meaning 5.0). However, MySQL 5.0 has reached "End of
Moreover, we have a performance problem in phpMyAdmin 4.0 and 4.1, due
to the navi panel mostly using INFORMATION_SCHEMA, which is poorly
implemented in older MySQL versions. This performance problem is seen on
servers with many (thousands?) of databases, which is not uncommon for
host providers. We have bug tickets about this.
By the way, using INFORMATION_SCHEMA helps us for some features like the
db filter (now with REGEX). I'm not sure how we could implement this
efficiently with SHOW DATABASES.
I would like to increase the minimum MySQL version for phpMyAdmin 4.1. I
got feedback from someone I trust, who is running MySQL 5.6 with
thousands of real-world databases and did some tests; on this version,
INFORMATION_SCHEMA performs ok.
If the team agrees, I would do some testing to find out at which point
INFORMATION_SCHEMA's fetch problems were fixed. Then we would advertise
this MySQL version as the minimum, and use only INFORMATION_SCHEMA in it
(no more SHOW DATABASES).
I believe that this is a good service to do to the community; it
resembles what we did when taking part in the GoPHP5 initiative.
> Date: Sat, 26 Oct 2013 18:44:28 +0100
> From: axel50397(a)gmail.com
> To: mynetx(a)users.sf.net
> Subject: Re: [Phpmyadmin-devel] [4.0.8] server_synchronize.php not found ?
> Le mardi 22 octobre 2013 à 15:29, J.M. . a écrit :
>> We removed the existing Synchronize feature because of serious flaws:
> Thank you for that information.
>> However, we plan to recreate an improved edition for a future version.
> Oh, same feature? Dev edition or just in a roadmap and no "preview" available ?
Let's say we have it in mind, but did not start development (yet).
You may want to open an RFE here and watch it:
>> In the meantime, I suggest you to take a look at MySQL’s own
>> replication feature, for keeping two database servers in sync.
> Of course, actually I was using the "sync" feature to make a sync first THEN a replication, and to copy the prod db in dev (some table). Anyway, thank you!
> Cordialement, Adnan RIHAN.
> Directeur-Gérant de Eolis-Software, société de services informatiques.
> $this->set("Mobile", "+33 (0) 6 78 62 26 20");
I am on Firefox 23, Windows 7. On current master, I was using the db
filter in navi, when I got "An error has occurred".
However, looking the Firebug console, I see, each second, a GET request
to error_report.php, followed by
TypeError: $nav_tree_content_position(...) is undefined
lines = stacktrace.split('\n');