| Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 63829 | 2011-12-21 19:34 | 2024-04-19 21:56 | MySQL Server: DML | Verified (4528 days) | S3 | 5.1.58, 5.5.20 | Any | Any | Search containig backslash doesn't work if field collation is utf8_unicode_ci |
| 36772 | 2008-05-16 23:04 | 2011-02-16 23:43 | MySQL Server: Charsets | Closed (5637 days) | S2 | 5.0BK/5.1BK/6.0BK | Any (Ubuntu (5.0.38-Ubuntu_0ubuntu1.4-log) and WinXP (5.0.45-community-nt)) | Any | When using UTF8, CONVERT with GROUP BY returns truncated results |
| 40026 | 2008-10-14 16:20 | 2008-10-14 20:37 | MySQL Server: DDL | Can't repeat (5692 days) | S2 | 5.1.26 | Any | Any | CREATE INDEX not online when using utf8 columns |
| 41279 | 2008-12-06 17:03 | 2011-02-16 23:43 | MySQL Workbench | No Feedback (5604 days) | S2 | 5.0.27 | Any | Any | Synchronization replaces COLLATION |
| 43055 | 2009-02-20 11:50 | 2011-02-16 23:43 | MySQL Server: Charsets | Closed (5563 days) | S2 | 5.0.32 | Any | Any | Connector/J causes data truncation error when inserting into latin1 text column |
| 45904 | 2009-07-02 10:43 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5175 days) | S1 | 5.1.34-community-log | Any | Any | Cannot create a key subpartition if character set of UTF8 is used |
| 47192 | 2009-09-08 16:13 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5317 days) | S3 | ALL | Any (Mac OS X 10.6) | Any | Wrong table format when using UTF8 strings |
| 59523 | 2011-01-15 8:02 | 2012-11-01 17:27 | MySQL Server: Charsets | Not a Bug (4213 days) | S2 | 5.0, 5.1 | Any | Any | LOAD DATA (LOCAL) INFILE does not work for UTF8 |
| 61483 | 2011-06-10 16:59 | 2011-06-10 18:01 | Connector / J | Closed (4723 days) | S2 | MySQL 5.5.13, Connector/J 5.1.16 | Any (Windows XP, Mac OS X) | Any | connector/J not correctly handling Korean characters |
| 86310 | 2017-05-13 11:31 | 2017-05-13 23:47 | MySQL Server: Command-line Clients | Verified (2559 days) | S3 | 5.6\5.7\8.0 | Any | Any | multibyte delimiter doesn't work |
| 62945 | 2011-10-26 15:47 | 2012-07-06 15:37 | MySQL Server: Charsets | Not a Bug (4331 days) | S3 | 5.5.15 | Any (7, x64) | Any | Like not work correctly for slovakian collate |
| 64205 | 2012-02-02 5:21 | 2012-05-25 20:43 | Connector / J | Closed (4373 days) | S3 | 5.1.18 | Any | Any | Connected through Connector/J 5.1 to MySQL 5.5, the error message is garbled. |
| 64578 | 2012-03-07 7:59 | 2012-07-06 15:34 | MySQL Server: Charsets | Not a Bug (4331 days) | S3 | 5.1.59-community-log, 5.1.63, 5.5.23, 5.6.6 | Any | Any | UTF8 is not UTF8 ? |
| 49712 | 2009-12-15 13:05 | 2009-12-15 13:25 | MySQL Server: Charsets | Not a Bug (5265 days) | S3 | 5.0.72 | Any | Any | bad search with utf8_polish_ci, and letter "รก" |
| 80631 | 2016-03-07 8:01 | 2016-10-14 16:02 | Connector / J | Closed (2800 days) | S2 | 5.1.38, 5.1.39, 6.0.3 | Any | Any | ResultSet.getString return garbled result with json type data |
| 64354 | 2012-02-16 15:45 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (4472 days) | S1 | 7.2.4 GA | Any | Any | LIKE function does not work in MySQL Cluster 7.2.4 for UTF8 char/varchar fields |
| 66480 | 2012-08-21 9:04 | 2018-11-24 8:37 | MySQL Server: Data Types | Verified (4285 days) | S3 | 5.5.27, 5.5.28 | Any (Squeeze) | Any | Myql comparison of curtime() with a constant in utf8 |
| 64634 | 2012-03-13 13:11 | 2012-04-01 10:56 | MySQL Server: Optimizer | Verified (4427 days) | S3 | 5.6.4-m7 | Any | Any | No result when binding to same field with different trailing spaces |
| 78340 | 2015-09-05 15:53 | 2015-10-09 14:41 | MySQL Server: Documentation | Closed (3141 days) | S3 | 5.7 | Any | Any | Downgrade advice for unicode not correct |
| 71778 | 2014-02-20 11:03 | 2014-02-20 11:09 | MySQL Server: Charsets | Not a Bug (3737 days) | S3 | 5.6 | Any | Any | latin1 accepts characters from cp1252 (as 0x92) but can't convert them to utf8 |
| 79597 | 2015-12-10 19:47 | 2018-05-17 16:15 | MySQL Server: Charsets | Closed (2190 days) | S3 | 5.6.24, 5.7.10 | Any | Any | "load data infile" is limited to ASCII characters as field enclosers |
| 71964 | 2014-03-07 9:02 | 2015-08-13 17:38 | MySQL Server: Documentation | Closed (3198 days) | S3 | 5.6.16 | Any | Any | Explanation of InnoDB physical row structure for CHAR is not clear. |
| 74701 | 2014-11-05 16:25 | 2014-11-06 6:57 | MySQL Server: Charsets | Verified (3478 days) | S3 | 5.6.21 | Any | Any | CONVERT TO CHARACTER SET combined with MODIFY COLUMN leads to unexpected results |
| 74816 | 2014-11-12 12:28 | 2015-08-17 16:45 | MySQL Server: DDL | Verified (3471 days) | S3 | 5.6.21, 5.6.23, 5.7.6 | Any | Any | Work around for charset conversion with FKs can result in wrong data |
| 78348 | 2015-09-06 9:09 | 2015-09-07 7:38 | MySQL Server: Command-line Clients | Closed (3173 days) | S3 | 5.7.8 | Any | Any | mysqlpump support for 4-byte UTF-8 |
| 21347 | 2006-07-30 9:36 | 2007-06-29 11:25 | MySQL Server | Not a Bug (6165 days) | S1 | 5.0 | Any (Linux, OpenBSD) | Any | hebrew utf8 ORDER BY produces bad results in OpenBSD MySQL 5.0 |
| 31555 | 2007-10-12 8:07 | 2011-02-16 23:43 | MySQL Server: Charsets | Closed (5077 days) | S3 | 5.0.27, 4.1, 5.0, 5.1, 5.2 BK | Any | Any | IFNULL(some_field, 123) doesn't convert charset from UTF8 |
| 99694 | 2020-05-26 13:06 | 2020-06-01 15:23 | MySQL Server: Charsets | Verified (1444 days) | S5 | 8.0 | Any | Any | Improving performance of my_hash_sort_utf8(mb4)/my_strnncollsp*utf8(mb4) |
| 93626 | 2018-12-15 21:22 | 2019-01-30 15:14 | MySQL Server: Charsets | Closed (1932 days) | S3 | 8.0.11 | Any | Any | Unicode string incorrectly marked as invalid |
| 100182 | 2020-07-10 13:35 | 2020-07-13 12:40 | MySQL Server: InnoDB storage engine | Verified (1405 days) | S5 | 8.0.20 | Any | ARM | Improving performance of 'row_mysql_store_col_in_innobase_format' |
| Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
