https://bugs.kde.org/show_bug.cgi?id=462268
Tuomas Nurmi <tuo...@norsumanageri.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tuo...@norsumanageri.org
--- Comment #1 from Tuomas Nurmi <tuo...@norsumanageri.org> ---
Also encountering this myself with some podcast.
The problem seems to be that databases are created with utf8mb3 character set,
but full UTF8 support would require them to be utf8mb4, detailed e.g. at
https://stackoverflow.com/questions/1168036/how-to-fix-incorrect-string-value-errors
, so some UTF8 characters fail to get saved to database. Looking through
existing and new mariadb databases, the column type seems to be utf8mb3
everywhere.
Comment at mariadb documentation
https://mariadb.com/kb/en/supported-character-sets-and-collations/
"The intention I believe is at some point to switch off the default old mode
setting, so that utf8 will then be an alias for utf8mb4."
MySQL seems to be further already, documentation at
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb3.html :
"The recommended character set for MySQL is utf8mb4. All new applications
should use utf8mb4. The utf8mb3 character set is deprecated. utf8mb3 remains
supported for the lifetimes of the MySQL 8.0.x and following LTS release
series, as well as in MySQL 8.0.
Expect utf8mb3 to be removed in a future major release of MySQL. "
Will need some database schema migration. Should be pretty straightforward, but
needs a lot of care. Last one seems to have been done in 2012.
--
You are receiving this mail because:
You are watching all bug changes.
