Hi,
I just saw that in our composer.json, the dependencies in require-dev
section are using ">=".
Composer deals with version number, considering that projects are following
semantic versioning (see http://semver.org/). And in this "standard", there
is one important thing: "Given a version number
MAJOR.MINOR.PATCH, increment the MAJOR version when you make incompatible
API changes". That means that 4.8 (current version) of PHPUnit might not be
compatible with 3.7, while an hypothetical 3.50 should be compatible. (In
reality… 3.7.7 is the last, for now.)
Knowing this, and to be sure that we won't have bad surprises, shouldn't we
use "~3.7"? And so replace:
* "require-dev": {*
* "satooshi/php-coveralls": ">=0.6",*
* "phpunit/phpunit": ">=3.7",*
* "phpunit/phpunit-selenium": ">=1.2",*
* "squizlabs/php_codesniffer": "2.*"*
* },*
by
* "require-dev": {*
* "satooshi/php-coveralls": "~0.6",*
* "phpunit/phpunit": "~3.7",*
* "phpunit/phpunit-selenium": "~1.2",*
* "squizlabs/php_codesniffer": "2.*"*
* },*
?
And if we really want to use PHPUnit 4.*, so let's fill the version with
"~4.8".
All these dependencies are for dev, so this won't be a big deal if versions
are not compatible, but this could leads to errors with PHPUnit the day it
will have an incompatible version.
What do you think about this?
Thanks for your feedbacks,
H.
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
development team).
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['NavigationTreeDefaultTabTable'], $cfg['DefaultTabServer'],
$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
Welcome to phpMyAdmin 4.4.15, the last bugfix release in the 4.4 family
(except for urgent fixes until March 31, 2016).
See https://www.phpmyadmin.net/files/4.4.15/.
--
The phpMyAdmin team
Hi,
This is related to [0]. According to [1] we should replace the
PmaAbsoluteUri directive with PmaUri, which would accept relative URLs.
Or maybe we don't need this directive anymore.
See mainly checkPmaAbsoluteUri().
It's a little late for 4.5.0 and even for 4.5.x, so I suggest we target
4.6 for this.
[0] https://github.com/phpmyadmin/phpmyadmin/issues/11412
[1] https://en.wikipedia.org/wiki/HTTP_location
--
Marc Delisle | phpMyAdmin
Howdy phpMyAdmin devs.
Looking at phpMyAdmin 4.5.0rc I notice the new "sql-parser" library.
=> No bundled library rules
I think this is:
https://github.com/dmitry-php/sql-parser
But this one seems stalled (June) while the version in phpMyAdmin 4.5
have more recent changes (August).
Questions:
- as dmitry-php/sql-parser is registered on packagist, will it be
updated soon ?
- a "rc" release could be nice (in sync with phpMyAdmin RC)
- a "stable" release could be nice (perhaps in sync with phpMyAdmin 4.5)
- why not use a git sub-modules to keep change easy ?
Current master version submitted to review for Fedora [1] to be usable
from phpMyAdmin, but of course, need to be updated first.
And vendor_config.php also need to be updated (patch attached)
Regards,
Remi.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1262807
Hi,
I suggest that after the 4.4.15 release (due on Sept. 20), we stop
working on 4.4 (apart from security fixes). This would mean deleting
QA_4_4 after the 4.4.15 release and stopping its translation efforts.
The reason is that 4.5.0 is due on Sept. 23.
--
Marc Delisle | phpMyAdmin
Hi everyone,
It seems that the namespacing of all pMA classes and usage of autoloading
is over (see https://github.com/phpmyadmin/phpmyadmin/pull/11428).
For we, with this, we should be PSR-4 compatible.
As there is a lot of files changed behind this and the loading is not
totally the same, would it be possible that some of you test this PR please
and give me some feedbacks?
Thanks,
H.
Le 2015-09-10 03:58, Nikul Chauhan a écrit :
> Hello,
>
> I am Getting Error while uploading database *“No data was received to
> import.
(...)
Hello,
this is not a support list, see https://www.phpmyadmin.net/support/.
--
Marc Delisle | phpMyAdmin
