Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MysqlSchemaTest::testDescribeTable fails with latest mysql version #16656

Closed
othercorey opened this issue Jul 29, 2022 · 4 comments · Fixed by #16670
Closed

MysqlSchemaTest::testDescribeTable fails with latest mysql version #16656

othercorey opened this issue Jul 29, 2022 · 4 comments · Fixed by #16670
Labels
Milestone

Comments

@othercorey
Copy link
Member

Description

1) Cake\Test\TestCase\Database\Schema\MysqlSchemaTest::testDescribeTable
Field definition does not match for title
Failed asserting that two arrays are equal.
--- Expected
+++ Actual
@@ @@
     'length' => 20
     'precision' => null
     'comment' => 'A title'
-    'collate' => 'utf8_general_ci'
+    'collate' => 'utf8mb3_general_ci'
 )

CakePHP Version

4.4

PHP Version

No response

@LordSimal
Copy link
Contributor

This is because of the latest change in MySQL 8.0.30
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-30.html

Important Change: A previous change renamed character sets having deprecated names prefixed with utf8_ to use utf8mb3_ instead. In this release, we rename the utf8_ collations as well, using the utf8mb3_ prefix; this is to make the collation names consistent with those of the character sets, not to rely any longer on the deprecated collation names, and to clarify the distinction between utf8mb3 and utf8mb4. The names using the utf8mb3_ prefix are now used exclusively for these collations in the output of SHOW statements such as SHOW CREATE TABLE, as well as in the values displayed in the columns of Information Schema tables including the COLLATIONS and COLUMNS tables.

@markstory markstory added this to the 4.4.4 milestone Jul 30, 2022
@markstory
Copy link
Member

Well that makes our lives harder as we need to span multiple versions of MySQL.

@othercorey
Copy link
Member Author

I don't understand why they don't do normal point releases for this stuff instead of just saying 5 patch releases is enough time to remove a deprecated feature.

@markstory
Copy link
Member

Oracle gonna oracle.

@markstory markstory linked a pull request Aug 4, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants