| Showing 1-30 of 88 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 75001 | 2014-11-25 23:55 | 2014-12-09 20:59 | MySQL Server: Charsets | Verified (3423 days) | S3 | 5.5.42, 5.6.23, 5.7.6 | Any | Any | CONCAT() of columns with same encoding but different collations behaves wrongly |
| 86517 | 2017-05-31 8:02 | 2017-06-13 16:48 | MySQL Server: Charsets | Verified (2506 days) | S3 | 5.7.17 | Any | Any | Tend to ER_OUT_OF_SORTMEMORY on UTF8MB4_UNICODE_CI much frequently (than UTF8MB4 |
| 86233 | 2017-05-09 3:22 | 2020-04-27 16:24 | MySQL Server: Charsets | Verified (1457 days) | S3 | 8.0 | Any | Any | NVARCHAR should default to utf8mb4 |
| 82349 | 2016-07-26 19:10 | 2018-03-28 9:00 | MySQL Server: Charsets | Verified (2218 days) | S3 | 5.5, 5.6 | Linux | Any | charset utf8mb4 is missing from /usr/share/mysql/charsets/Index.xml |
| 80076 | 2016-01-20 13:55 | 2016-01-21 6:02 | MySQL Server: Charsets | Verified (3015 days) | S3 | 5.5.47, 5.6.28, 5.7.10 | Any | Any | "SELECT... INTO OUTFILE ... CHARACTER SET ucs2" writes non-standard <eol> chars |
| 80075 | 2016-01-20 13:26 | 2016-01-21 5:52 | MySQL Server: Charsets | Verified (3015 days) | S3 | 5.5.47, 5.6.28, 5.7.10 | Any | Any | "SET sql_mode=..." generates an error when @@character_set_connection=ucs2 |
| 79989 | 2016-01-14 16:25 | 2016-01-18 12:31 | MySQL Server: Charsets | Verified (3018 days) | S3 | 5.5.47, 5.6.28, 5.7.10, 5.5.48, 5.6.29, 5.7.11 | Any | Any | "USE <db>" doesn't always change @@character_set_database to <db>'s charset |
| 78371 | 2015-09-08 19:59 | 2015-09-09 7:27 | MySQL Server: Charsets | Verified (3149 days) | S3 | 5.7.8, 5.7.9 | Any | Any | Dumpfile with utf16 can't |
| 77993 | 2015-08-08 9:27 | 2017-09-18 7:26 | MySQL Server: Charsets | Verified (3181 days) | S3 | 5.6.26, 5.7.8 | CentOS (CentOS 7) | Any | handle_fatal_signal (sig=6) in my_mbcharlen_utf16 | /strings/ctype-ucs2.c:1421 |
| 76215 | 2015-03-09 1:57 | 2015-03-11 12:48 | MySQL Server: Charsets | Verified (3331 days) | S3 | 5.5.44, 5.6.25 | Any | Any | Implicit casts to string by COLLATE don't use character_set_connection |
| 75483 | 2015-01-12 19:02 | 2015-01-14 13:33 | MySQL Server: Charsets | Verified (3387 days) | S1 | 5.5.28, 5.6.24, 5.5.42 | Any | Any | Mysqldump bit information dumped in the txt file has whitespace |
| 86622 | 2017-06-08 12:15 | 2020-01-07 13:16 | MySQL Server: Charsets | Verified (1568 days) | S3 | 5.6, 5.7, 8.0 | Linux | Any | Character comparison incorect |
| 74817 | 2014-11-12 13:22 | 2014-11-13 6:25 | MySQL Server: Charsets | Verified (3449 days) | S3 | 5.6.15, 5.6.21 | Windows (Windows 7) | Any | Character set issue with view |
| 74701 | 2014-11-05 16:25 | 2014-11-06 6:57 | MySQL Server: Charsets | Verified (3456 days) | S3 | 5.6.21 | Any | Any | CONVERT TO CHARACTER SET combined with MODIFY COLUMN leads to unexpected results |
| 74449 | 2014-10-20 9:39 | 2014-10-20 10:44 | MySQL Server: Charsets | Verified (3473 days) | S3 | 5.5.40, 5.6.21, 5.7.5, 5.6.22 | Linux (CentOS 6.3) | Any | Incorrect datetime casting with charcter_set_connection=sjis |
| 74429 | 2014-10-17 11:25 | 2016-06-17 14:32 | MySQL Server: Charsets | Verified | S3 | 5.7.5 | Any | Any | system_time_zone generates warning if zone name contains non-ascii chars |
| 73153 | 2014-06-30 22:10 | 2016-07-20 10:48 | MySQL Server: Charsets | Verified (3584 days) | S3 | 5.6, 5.6.20, 5.7.5 | Linux | Any | CONVERT TO CHARACTER SET utf8 doesn't change DEFAULT CHARSET |
| 73086 | 2014-06-23 23:56 | 2014-06-24 4:48 | MySQL Server: Charsets | Verified (3591 days) | S3 | 5.5.8, 5.5.31, 5.5.34, 5.6.19 | Any | Any | Collation and coercibility of AVG(NULL) is incorrectly reported as "binary" |
| 72882 | 2014-06-05 2:24 | 2014-07-25 19:51 | MySQL Server: Charsets | Verified (3560 days) | S5 | 5.5 5.6 | Linux | Any | Metadata character set causes unnecessary cost for cpu-bound scene |
| 72715 | 2014-05-21 22:39 | 2014-05-22 8:02 | MySQL Server: Charsets | Verified (3624 days) | S3 | 5.6.17 | Any | Any | character set code endianness dependent on CPU type rather than endianness of CP |
| 72685 | 2014-05-19 20:20 | 2014-05-20 7:01 | MySQL Server: Charsets | Verified (3626 days) | S2 | 5.5.31, 5.5.34, 5.6.19, 5.7.5 | Any | Any | LOCATE/INSTR with mixed collations returns inconsistent results |
| 70815 | 2013-11-05 3:43 | 2014-05-21 19:00 | MySQL Server: Charsets | Verified (3625 days) | S2 | 5.5.31, 5.5.34 | Any | Any | SELECT DISTINCT hashes Unicode space characters incorrectly |
| 106389 | 2022-02-07 5:44 | 2022-02-07 6:10 | MySQL Server: Charsets | Verified (806 days) | S3 | 8.0 | Any (N/A) | Any | What is the next step in making utf8 and utf8mb4 synonyms? |
| 114195 | 2024-03-02 15:24 | 2024-03-04 6:56 | MySQL Server: Charsets | Verified (50 days) | S3 | 8.0.36 | Any | Any | mysql doesn't show what collation was used sometimes |
| 114086 | 2024-02-21 19:41 | 2024-02-26 11:05 | MySQL Server: Charsets | Verified (57 days) | S3 | 8.0 | Any | Any | Item_singlerow_subselect::store may lead to memory corruption |
| 113933 | 2024-02-08 15:38 | 2024-02-08 17:16 | MySQL Server: Charsets | Verified (75 days) | S3 | 8.0 | Any | Any | Contribution: Fix multibyte bugs in my_instr_mb |
| 113537 | 2024-01-02 16:00 | 2024-01-04 10:44 | MySQL Server: Charsets | Verified (110 days) | S3 | 8.0.32 | Any | Any | False match of multibyte chars when checking existence of a control character |
| 113506 | 2023-12-25 2:26 | 2024-01-03 17:06 | MySQL Server: Charsets | Verified (120 days) | S2 | 8.0,8.0.35, 8.1.0, 8.2.0 | Any | Any | Item_func_conv_charset::eq not correct |
| 111268 | 2023-06-04 17:21 | 2023-06-06 11:00 | MySQL Server: Charsets | Verified (323 days) | S3 | 8.0.25, 8.0.33 | Any | Any | Different character_set_connection returns inconsistent results |
| 110825 | 2023-04-26 23:58 | 2023-04-27 8:29 | MySQL Server: Charsets | Verified (362 days) | S3 | 8.0.32 | Any | Any | Explicit COLLATE clause output in SHOW CREATE TABLE incorrectly |
| Showing 1-30 of 88 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
