Hi phpmyadmin developers,
I just downloaded 4.5.0-beta1. I love that you are using the ALTER USER command from 5.7!
I have some specific 5.7 features to mention that you may be able to make use of:
1) The server now supports a list of disabled_storage_engines (these still “work” but no new tables can be created).
It might make sense to remove them from the drop-down-list or make them appear greyed out.
They also appear under “ENGINES” the same as others currently.
2) The STATUS > PROCESSLIST is currently using SHOW PROCESSLIST. In MySQL 5.7, there will be SELECT * FROM sys.x$processlist or SELECT * FROM sys.x$sessions (user connections only). This has some added context (transactions open, memory usage etc) and the command itself uses fewer locks than SHOW PROCESSLIST. Here is an example of output:
3) The datatype JSON does not appear to be added yet. 5.7.8 added this native type with ~20 JSON manipulation functions.
MySQL Community Manager
Oracle Canada - Hardware and Software, Engineered to Work Together.
Office: Toronto, Canada
looking at , PHP 5.3 is EOL. I suggest that for phpMyAdmin 4.5 we
state that PHP 5.4 is the minimum. Doing so, we would have less testing
to do, and we would help promote using a PHP supported version.
I would even suggest PHP 5.5 as the minimum, because the end of security
support for PHP 5.4 occurs in less than one month.
Marc Delisle | phpMyAdmin
phpMyAdmin's ruleset is based on PEAR standards. One of this standard
(PEAR_Sniffs_NamingConventions_ValidVariableNameSniff) is to name class'
attributes / methods with a leading underscore when the element is
protected / private.
This rule is quite useful because it helps to see very quickly if an
element is public or not. But
http://www.php-fig.org/psr/psr-2/#4-2-properties asks not to use this
For attributes, I'm not sure this is a big deal because almost all the
attributes shouldn't be visible and accessible only by getters / setters.
But for methods, there is nothing to know the visibility of a method.
However actual IDE help to see this.
Do you think that we should follow PSR2? Only for attributes maybe?
Should we consider to base our ruleset on another standard closest to PSR
Thanks for your feedback,
Welcome to phpMyAdmin 4.5.0, which includes many improvements thanks to
our Google Summer of Code students and other contributors. With this
release, the minimum required PHP version is now 5.5 (older versions
have reached End of Life and are no longer supported by the PHP
A complete list of new features and bugs that have been fixed is
available in the ChangeLog file or changelog.php included with this release.
A few highlights:
* Improvements to the Console feature
* Include structure in PDF export
* Validate data before import
* Support CHECKSUM TABLE operation
* Improved operations regarding partitions
* Alter privileges when renaming or copying a database or table
* Several improvements related to speed and responsiveness
* Improved print view
* Use CTRL or ALT plus arrow keys to navigate in grid editor
* Use plain-English destinations for
$cfg['DefaultTabDatabase'], and $cfg['DefaultTabTable']. The old style
values will still work, but this makes it easier for new users to easily
understand the destination links.
* Integrate SQL debugging into Console
* Restore row editing when no unique/primary key exists
* Allow exporting one file per table and one file per database
* Improvements to using multiple servers with the auth_type cookie
* Support virtual columns (MySQL 5.7.5+)
* Add or improve support for several MariaDB features including process
list and virtual/persistent columns
* Improved handling of cached data when upgrading phpMyAdmin
* Add SHA256 security password support
There are many more; please refer to the ChangeLog for full details.
As always, downloads are available at http://www.phpmyadmin.net
The phpMyAdmin Team