| Showing all 20 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 51907 | 2010-03-10 12:26 | 2021-05-02 20:45 | MySQL Server: Tests | Verified (5133 days) | S3 | 5.5.3 | Any | Any | main.ctype_utf8mb4_ndb fails persistently |
| 62453 | 2011-09-16 20:33 | 2011-09-17 9:49 | MySQL Workbench | Not a Bug (4604 days) | S3 | 5.2.34 | Windows (Win XP x32) | Any | Workbench deletes 4byte utf8 symbols without notification and inserts the string |
| 62442 | 2011-09-15 11:50 | 2011-09-16 20:03 | MySQL Server: Charsets | Not a Bug (4605 days) | S3 | 5.5.13.0 | Windows (Win 7 x64, win xp sp3) | Any | Some symbols cannot be inserted into UTF-8 default charset field (VARCHAR(255)) |
| 69021 | 2013-04-21 11:06 | 2013-05-01 10:01 | Connector / ODBC | Verified (4012 days) | S3 | 5.2.4 | Windows (7) | Any | Results with character set utf8mb4 do not convert correctly in classic ASP |
| 71964 | 2014-03-07 9:02 | 2015-08-13 17:38 | MySQL Server: Documentation | Closed (3178 days) | S3 | 5.6.16 | Any | Any | Explanation of InnoDB physical row structure for CHAR is not clear. |
| 78348 | 2015-09-06 9:09 | 2015-09-07 7:38 | MySQL Server: Command-line Clients | Closed (3153 days) | S3 | 5.7.8 | Any | Any | mysqlpump support for 4-byte UTF-8 |
| 81196 | 2016-04-26 1:40 | 2018-09-27 23:41 | Connector / J | Closed (2086 days) | S2 | 5.1.38+ | Any | Any | Connector/J Not Following Database character set |
| 86454 | 2017-05-25 7:34 | 2018-05-16 19:18 | MySQL Workbench | Closed (2171 days) | S2 | 6.3.9 | Windows (commercial version) | Any | Workbench can't process utf8mb4 encode |
| 81677 | 2016-06-01 13:00 | 2018-04-23 1:00 | MySQL Server: JSON | No Feedback (2195 days) | S3 | 5.7 | Any | Any | Allows to force JSON columns encoding into pure UTF-8 |
| 93626 | 2018-12-15 21:22 | 2019-01-30 15:14 | MySQL Server: Charsets | Closed (1912 days) | S3 | 8.0.11 | Any | Any | Unicode string incorrectly marked as invalid |
| 97569 | 2019-11-10 7:00 | 2019-11-11 5:49 | Connector / C | Not a Bug (1627 days) | S3 | 8.0.18 | Ubuntu (16.04) | x86 | Connector is inserting Japanese as gibberish when using utf8 charset |
| 99732 | 2020-05-28 21:50 | 2021-02-27 6:05 | Connector / ODBC | Not a Bug (1423 days) | S2 | 5.3.14 | Windows (Win10, Win 2012 Srv) | Any (x86, x64) | ODBC driver fails to return 4-byte UTF-8 characters |
| 104066 | 2021-06-21 7:00 | 2023-11-24 13:22 | MySQL Server: Options | Verified (1039 days) | S3 | 8.0.23, 8.0.25 | Linux | Any | Inconsistency of description for default_collation_for_utf8mb4 |
| 101346 | 2020-10-27 16:05 | 2021-11-25 7:49 | MySQL Server: Prepared statements | Closed (1273 days) | S3 | 8.0.22 | Ubuntu (18.04) | x86 | "Illegal mix of collations" errors when matching ascii field and unicode |
| 106389 | 2022-02-07 5:44 | 2022-02-07 6:10 | MySQL Server: Charsets | Verified (808 days) | S3 | 8.0 | Any (N/A) | Any | What is the next step in making utf8 and utf8mb4 synonyms? |
| 105077 | 2021-09-29 15:31 | 2021-10-07 13:41 | MySQL Server: Charsets | Not a Bug (938 days) | S3 | 8.0.26 | Any | Any | As of 8.0.26, mysqldump substitutes utf8mb3 for utf8 |
| 88657 | 2017-11-25 23:33 | 2022-03-25 18:02 | Connector / Python | Closed (762 days) | S2 | 2.1.7 | Any | Any | LookupError: unknown encoding: utf8mb4 |
| 83461 | 2016-10-20 12:59 | 2023-01-11 8:15 | MySQL Server: Replication | Can't repeat (470 days) | S3 | 8.0.0, 8.0.18, 5.7.28 | Any | Any | replication breakage noted from 5.7.10 to 8.0.0 |
| 109699 | 2023-01-19 10:34 | 2023-06-12 9:59 | MySQL Server: Optimizer | Closed (448 days) | S2 | 8.0.32 | Any | Any | utf8mb4 identifiers stopped working since 8.0.32 release |
| 114542 | 2024-04-03 8:36 | 2024-04-03 13:18 | MySQL Server: Prepared statements | Not a Bug (22 days) | S3 | 8.0.36-commercial | Any (8) | Any | Encoding issue when reusing Prepared Statement |
| Showing all 20 (Edit, Save, CSV, Feed) |
