New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trunk: ArchiveProcessingTest detect when bulk insert is testable #3605
Comments
(In [7600]) fixes #3605 - add detection for mysqlnd |
(In [7601]) refs #3605 - correct information in phpdocs |
All in all, what is the minimum recommended php version? is the latest 5.3.x enough to enjoy LOAD DATAINFILE. Since it's a big improvement boost, we could add it in the system check list as a "warning" - high traffic users will want to know this setting. Otherwise this ticket cna be closed since tests pass? Thanks so much for finding this info it was doing my head in! we are going green |
Minimum:
Maximum:
|
Thanks added comment in: #2122 |
@vipsoft I would like to follow up [7600] and add a warning if box is Jenkins AND isBulkInsertTestable() returns false (since we should know when jenkins stops running these tests). how could we detect if the current server is Jenkins? |
(In [7677]) Fixes #3605 Marking the test as "skipped" even if it's not testable. This will be annoying to always see it in the test output so I probably disable it for jenkins later |
The ArchiveProcessing test using Mysqli is passing when using LOAD DATA INFILE, so it isn't a MySQL / AppArmor configuration issue. (I also checked that the "piwik" db user has the FILE privilege.)
On the VM, the mysqli.so and pdo_mysql.so extensions both appear to use libmysqlclient. On dev6, our 5.3.x builds used the new mysqlnd (native driver) extension.
So, this points to a pdo_mysql bug ... i.e.,
The text was updated successfully, but these errors were encountered: