Régis Behmo 2a47100d6a fix: broken mysql after palm upgrade ... This fix is for a rather serious issue that affects users who upgrade from Olive to Palm. The client mysql charset and collation was incorrectly set to utf8mb4, while the server stil runs utf8mb3. Only users who run the mysql container are affected. To resolve this issue, we explicitely configure the client to use the utf8mb3 charset/collation. Important note: users who have somehow managed to upgrade from olive to Palm before may find themselves in an undefined state. They might have to fix their mysql data manually. Same thing for users who launched Palm from scratch; although, according to my preliinary tests, they should be able to downgrade their connection from utf8mb4 to utf8mb3 without issue. In addition, we upgrade to mysql 8.1.0. Among many other fixes, this avoids a server restart after the upgrade: > An in-place upgrade from MySQL 5.7 to MySQL 8.0, without a server > restart, could result in unexpected errors when executing queries on > tables. This fix eliminates the need to restart the server between the > upgrade and queries. (Bug #35410528) https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-34.html See also the 8.1.0 release notes: https://dev.mysql.com/doc/relnotes/mysql/8.1/en/news-8-1-0.html Close #887.		2023-08-16 19:01:41 +02:00
..
scriv	fix: scriv error during github release	2023-06-14 09:38:07 +02:00
20230731_110301_regis_fix_non_buildkit_build.md	fix: improve support of non-buildkit Docker build	2023-08-16 18:56:59 +02:00
20230815_064652_regis_fix_mysql_upgrade_charset.md	fix: broken mysql after palm upgrade	2023-08-16 19:01:41 +02:00
20230816_184458_regis_fix_local_non_prod.md	fix: ask whether we run as prod in local launch	2023-08-16 18:57:26 +02:00
scriv.ini	ci: better github release management with scriv	2023-01-17 12:12:10 +01:00