You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/main/core-api/java/com/mysql/cj/CharsetSettings.java
+2-2
Original file line number
Diff line number
Diff line change
@@ -54,13 +54,13 @@ public interface CharsetSettings {
54
54
* </ol>
55
55
* otherwise it will be set to utf8mb4_general_ci or utf8mb4_0900_ai_ci depending on server version.
56
56
* <p>
57
-
* Since Protocol::HandshakeV10 and Protocol::HandshakeResponse41 has only one byte for the collation it's not possible to use indexes > 255 during the
57
+
* Since Protocol::HandshakeV10 and Protocol::HandshakeResponse41 use only one byte for the collation it's not possible to use indexes > 255 during the
58
58
* handshake.
59
59
* Also, ucs2, utf16, utf16le and utf32 character sets are impermissible here. Connector/J will try to use utf8mb4 instead.
60
60
* </p>
61
61
*
62
62
* @param reset
63
-
* reset the charsets configuration; needed for changeUser call.
63
+
* reset the charsets configuration; needed for changeUser and resetServerState call.
64
64
*
65
65
* @return MySQL collation index to be used during the handshake.
// If none of "passwordCharacterEncoding", "connectionCollation" or "characterEncoding" is specified then use UTF-8.
220
220
// It would be better to use the server default collation here, to avoid unnecessary SET NAMES queries after the handshake if server
221
-
// default charset if not utf8, but we can not do it until server Bug#32729185 is fixed. Server cuts collation index to lower byte and, for example,
222
-
// if the server is started with character-set-server=utf8mb4 and collation-server=utf8mb4_is_0900_ai_ci (collation index 257) the Protocol::HandshakeV10
223
-
// will contain character_set=1, "big5_chinese_ci". This is true not only for MySQL 8.0, where built-in collations with indexes > 255 were first introduced,
224
-
// but also other server series would be affected when configured with custom collations, for which the reserved collation id range is >= 1024.
221
+
// default charset if not utf8, but we can not do it until server Bug#32729185 is fixed. Server cuts collation index to lower byte and, for
222
+
// example, if the server is started with character-set-server=utf8mb4 and collation-server=utf8mb4_is_0900_ai_ci (collation index 257) the
223
+
// Protocol::HandshakeV10 will contain character_set=1, "big5_chinese_ci". This is true not only for MySQL 8.0, where built-in collations with
224
+
// indexes > 255 were first introduced, but also other server series would be affected when configured with custom collations, for which the
0 commit comments