Closed MichaelRoosz closed 8 months ago
@MichaelRoosz thanks for reporting this, will update the FAQ.
Hi @MichaelRoosz, Thanks again for reporting this. We've gone back and updated the FAQ you suggested with the following information:
Column size adjustment during utf8mb4 conversion One final note is that when upgrading your database to support
utf8mb4
, be aware that columns storing text data (such asTEXT
,MEDIUMTEXT
, etc.) will automatically increase in size to ensure the upgraded column can store as many characters as the source column. For example aMEDIUMTEXT
column will become aLONGTEXT
column. You will need to account for this if you’re manually updating your database schema or if you have specific data storage limits to ensure a smooth upgrade.
Can you please let me know if this adequately addresses your concerns?
Hello @danielmcclure looks good to me, thank you 👍
After upgrading to utf8mb4 via
./console core:convert-to-utf8mb4
as documented here: https://matomo.org/faq/how-to-update/how-to-convert-the-database-to-utf8mb4-charset/All columns of all tables of type "text" (text, mediumtext, etc) have automatically been increased in size by the sql server (MariaDb 10.7).
For example, before:
after:
The logic behind this is documented here: https://mariadb.com/kb/en/setting-character-sets-and-collations/#table-level
As this might be unexpected, I think it would be great to mention this behavior here: https://matomo.org/faq/how-to-update/how-to-convert-the-database-to-utf8mb4-charset/