Run a Travis job with the MySQL Extension

[dd32]

I just noticed that the PHP 5.2 job is running with MySQLi (which I didn't even realise was possible).

That ultimately means we have no automated testing which is testing the mysql_* functions in $wpdb which is used for PHP 5.2~5.4 by default.

The attached patch uses WP_USE_EXT_MYSQL to force it to use the MySQL extension for the PHP 5.2 job, I've tested this on ​my own travis account and it passes as expected, with the only change being an additional skipped test (which requires mysqli).

[netweb]

I've created a pull request to test 42811.diff​ ​https://github.com/WordPress/wordpress-develop/pull/9

[pento]

What an exciting time to be alive!

[dd32]

Just noticed I incorrectly referenced mysqli_* functions instead of mysql_* functions :)

[dd32]

I got to thinking - now that PHP 5.2 could legitimately be running MySQLi in production, we probably shouldn't take the route in 42811.diff​ directly.

Maybe this means we need another job dedicated to MySQL - although it doesn't need to be PHP 5.2, perhaps it could be a 5.6 job?
If we were to limit PHP 5.2 jobs to MySQL-only we'd miss out on the regular testing of the least-feature-complete version of MySQLi out there.

[pento]

With WordPress' PHP version bump coming up, let's just add an extra PHP 5.6 job that tests with ext/mysql.

[jorbin]

Bumping this from 5.2 due to lack of progress but as it is related to a test config and not something that directly affects the code we release, I'm happy to bring it back if there is progress.

[netweb]

Having this for PHP 5.6 is no longer an issue, the 42811.diff​ does need a refresh to match up with the new Docker'ised changes to Travis CI setup.

For now, punting this back to 'future release', feel free to move this back into the current milestone once the patch has been refreshed.

[jrf]

What with WP 5.6 slated to remove support for PHP 5.6, can this ticket be closed ?