Joomla 2.5 Mysql 8
The same applies to tinyint.
It's not possible to connect to a MySQL 8 Database using Joomla. The reason is that MySQL 8 has a lot of changes under the hood. One change that affects Joomla is the default authentication plugin which is sha256password instead of mysqlnativepassword. Actually, there should be one issue open somewhere tracking the progress of MySQL 8 compatibility in the CMS. Without that, items will be continually closed pointing to that docs page which gives the impression that Joomla is not making efforts to support MySQL 8 (hell it still doesn't fully support 5.7). Fnatic league of legends.
See related PR #28501 .
To get rid of the deprecation notices we can change our SQL scripts to not use display width values anymore for int and tinyint columns. But this has to include also all present update SQL scripts, not only the scripts for new installation.
The question is if we want to do this for staging and 3.10-dev and 4.0-dev, or only for 4.0-dev.
The deprecation notices became more urgent since the default value for the server configuration option to show these notices was not to show them by default, but this may have change with a recent 8.0.x version of MySQL.
Joomla Mysql 8
We have to keep in mind that MariaDB behaves differently and still supports display widths, as far as I know.
Joomla 2.5 Mysql 8
The same applies to tinyint.
It's not possible to connect to a MySQL 8 Database using Joomla. The reason is that MySQL 8 has a lot of changes under the hood. One change that affects Joomla is the default authentication plugin which is sha256password instead of mysqlnativepassword. Actually, there should be one issue open somewhere tracking the progress of MySQL 8 compatibility in the CMS. Without that, items will be continually closed pointing to that docs page which gives the impression that Joomla is not making efforts to support MySQL 8 (hell it still doesn't fully support 5.7). Fnatic league of legends.
See related PR #28501 .
To get rid of the deprecation notices we can change our SQL scripts to not use display width values anymore for int and tinyint columns. But this has to include also all present update SQL scripts, not only the scripts for new installation.
The question is if we want to do this for staging and 3.10-dev and 4.0-dev, or only for 4.0-dev.
The deprecation notices became more urgent since the default value for the server configuration option to show these notices was not to show them by default, but this may have change with a recent 8.0.x version of MySQL.
Joomla Mysql 8
We have to keep in mind that MariaDB behaves differently and still supports display widths, as far as I know.
Joomla Mysql 8 Vs
But Brian is absolutely right, these values never had any impact on accuracy, value range or storage size of such database columns, so they should never have been used at the beginning, and we safely can remove them after my PR #28501 has made the database checker clever enough to just ignore these display widths.
