#36419Migrate core from mysql to mysqli
Description
Without using dbal core still uses the mysql-extension instead of mysqli. But PHP officially claims mysql to be “legacy” and mysqli is shipped with PHP since quite a while now. Since PHP 5.3.0 now mysqli also supports persistent connections. So it should be “quite simple” to replace the few direct calls to mysql-functions with mysqli-equivalents. It’s just a different ressource (well, an object then) that is returned, so the inner parts in TYPO3 passing around the DB-handler can (almost) stay as is.
All extensions should use TYPO3-functionality to access the database, so no change should be required on that part. It might be that some directly execute mysql_query()-calls or the like, so this is kind of a “break”. But things are easy to fix – and then maybe they could switch to using the TYPO3-functions for it anyway :-)
Might this be a candidate for 6.0? Patch itself should be quite easy to do.
Reviews 4
Related issues 7
- Feature #16232support mysqli extension
- Bug #46330Install tool: PHP Runtime Deprecation Notice: mysql_list_dbs()
- Bug #46802Typo3DatabaseBackend get function does not return FALSE
- Bug #46805Integrity test fails
- Bug #46806fetch_field_redirect returns object but not array
- Bug #46825mysqli::real_connect() / Unknown MySQL server
- Bug #47090Database link is expected to be an object