Showing all 15 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
62077 | 2011-08-03 19:50 | 2014-05-28 9:24 | MySQL Server: General | Verified (4914 days) | S3 | 5.5.11, 5.5.16 | Any | Any | Assign date/time type to user-defined variable changes type/charset/collation |
64023 | 2012-01-13 12:57 | 2012-01-15 19:32 | MySQL Server: Charsets | Verified (4753 days) | S3 | 5.1.61, 5.5.16-log | Any | Any | STR_TO_DATE / DATE_FORMAT combination gives wrong values for non 'en_*' charsets |
55606 | 2010-07-28 15:25 | 2015-08-30 17:21 | MySQL Server: Charsets | Verified (4271 days) | S5 | 5.1.47, 5.1.50-bzr, 5.5.23, 5.6.11 | Linux | Any | Charset on ENUMS influencing performance too much |
68805 | 2013-03-28 16:30 | 2013-08-06 8:42 | MySQL Server: Command-line Clients | Verified (4182 days) | S3 | 5.6.13 | Any (Linux and Windows) | Any | client crashes after "charset utf16" |
67739 | 2012-11-28 9:29 | 2015-04-27 7:24 | MySQL Server: Charsets | Verified (4428 days) | S3 | All | Any | Any | GBK charset is not Fully supported in mysql |
73967 | 2014-09-18 12:35 | 2015-07-20 8:17 | MySQL Server: Performance Schema | Verified (3657 days) | S3 | 5.6.20 | Any | Any | Incorrect string value for sql_text |
96481 | 2019-08-09 7:47 | 2019-08-09 10:22 | MySQL Workbench | Verified (1988 days) | S3 | 8.0.17 | Windows | x86 | MySQL Workbench 8.0 shows wrong collation/charset for MySQL 5.6 tables |
104035 | 2021-06-16 10:50 | 2021-06-16 20:28 | MySQL Server: DML | Verified (1311 days) | S3 | 8.0/5.7 | Ubuntu (20) | Any | Strict SQLMode not honored in SP's based on DB charset |
105394 | 2021-10-31 23:46 | 2021-11-02 8:32 | MySQL Server: Charsets | Verified (1173 days) | S3 | all, 5.7, 8.0 | Any | Any | introducer _ucs2 not working |
106389 | 2022-02-07 5:44 | 2022-02-07 6:10 | MySQL Server: Charsets | Verified (1075 days) | S3 | 8.0 | Any (N/A) | Any | What is the next step in making utf8 and utf8mb4 synonyms? |
107500 | 2022-06-07 11:20 | 2022-06-07 11:29 | MySQL Server: Charsets | Verified (955 days) | S2 | any, 8.0 | Any | Any | Contribution by Tentent: Setting default-character-set does not take effect |
107109 | 2022-04-24 9:07 | 2023-04-14 13:24 | MySQL Server: Parser | Verified (956 days) | S2 | 8.0.27, 5.7.37, 8.0.32 | Any (rhel-7.4) | Any (x86-64) | Optimizer hints doesn't work if client charset is the same with charset of syste |
113537 | 2024-01-02 16:00 | 2024-01-04 10:44 | MySQL Server: Charsets | Verified (379 days) | S3 | 8.0.32 | Any | Any | False match of multibyte chars when checking existence of a control character |
114717 | 2024-04-20 18:57 | 2024-04-22 9:30 | MySQL Server: DDL | Verified (270 days) | S3 | 8.0.36 | Any | Any | Inconsistent behavior of explicit CHARSET/COLLATE column definition |
116584 | 2024-11-07 11:58 | 2024-11-10 6:46 | MySQL Server: Charsets | Verified (71 days) | S2 | 8.0.36, 8.0.40 | Any (Redhat 7.4) | Any (Intel) | Query produces different resultset with force index |
Showing all 15 (Edit, Save, CSV, Feed) |