WordPress.org

Make WordPress Core

Opened 3 months ago

Last modified 3 months ago

#53623 new defect (bug)

MariaDB 10.6 renamed utf8 to utf8mb3

Reported by: skithund Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Database Keywords: needs-patch
Focuses: Cc:

Description

See MariaDB ticket MDEV-8334 "Rename utf8 to utf8mb3"

Which results in charset tests are now failing.

Change History (4)

#1 @ayeshrajans
3 months ago

Very nice find :)
I suppose we can conditionally assertSame by checking the db version and the name.

From what I see, self::$server_info contains MariaDB, and self::$_wpdb->db_version() returns the version. I don't have a MariaDB test setup at the moment, and will try to put forth a patch this weekend. Just wanted to share my 2 cents in the meantime.

This ticket was mentioned in Slack in #forums by yui. View the logs.


3 months ago

This ticket was mentioned in Slack in #hosting-community by yui. View the logs.


3 months ago

#4 @ayeshrajans
3 months ago

MySQL 8.0.26 also has related changes: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-26.html


These statements now report utf8mb3 rather than utf8 when writing character set names: EXPLAIN, SHOW CREATE PROCEDURE, SHOW CREATE EVENT.

Stored program definitions retrieved from the data dictionary now report utf8mb3 rather than utf8 in character set references. This affects any output produced from those definitions, such as SHOW CREATE statements.

This error message now reports utf8mb3 rather than utf8 when writing character set names: ER_INVALID_CHARACTER_STRING. (Bug #32233614, Bug #32392077, Bug #32392209, Bug #32428538, Bug #32428598)

Note: See TracTickets for help on using tickets.