Request to support MySQL 8.0 latest collations: utf8mb4_0900_ai_ic, etc....

[Delphier]

MySQL 8.0 use utf8mb4_0900_ai_ci as default collation, but when set collation as this, an error occurs: unknown collation.

[methane]

New collations which id<256 should be added to collations.go.

[Delphier]

MySQL 8.0 has 270 collations, some collation id >255

[methane]

MySQL's handshake reserves only one byte for collation id.
So we can use only collation which id >= 256 in handshake.

And collation for connection is not so important, while encoding for connection is important.
Each column should have own collation and it's used for normal cases.

[Delphier]

OK, I get it now，that’s clear, thank you.

[julienschmidt]

How does e.g. the official MySQL client transmit collations > 255 then?
If it is supported there, we can add support too.

[methane]

Please don't close. collation id of utf8mb4_0900_ai_ic is 255. It should be supported.

[methane]

How does e.g. the official MySQL client transmit collations > 255 then?
If it is supported there, we can add support too.

MySQL client doesn't have API to specify collation. Only charset can be specified
and default collation for the charset is chosen.

When connection collation is really matters, client should:

1. Connect with utf8mb4_unicode_520_ci
2. SET NAMES utf8mb4 COLLATE <collation you really need>

Maybe, we can add collation support to charset option. For example, charset=utf8mb4: utf8mb4_ja_0900_as_cs.

[jason-gu]

Hi, I see a pull request ready for this issue, will it be merged anytime soon, so we can to use utf8mb4_0900_ai_ci (default for MySQL 8.x)?

[xtianus79]

I am receiving the same error.

ERROR 1273 (HY000) at line 1: Unknown collation: 'utf8mb4_0900_ai_ci'

[xtianus79]

sorry I mistakenly didn't update my server... I only updated workbench.