| Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 62728 | 2011-10-13 22:59 | 2024-04-23 10:07 | Connector / ODBC | Can't repeat | S2 | 5.1.8 | Windows | Any | ODBC Connector 5.1 utf8 stored incorrectly |
| 83461 | 2016-10-20 12:59 | 2023-01-11 8:15 | MySQL Server: Replication | Can't repeat (468 days) | S3 | 8.0.0, 8.0.18, 5.7.28 | Any | Any | replication breakage noted from 5.7.10 to 8.0.0 |
| 89275 | 2018-01-17 2:04 | 2018-01-17 8:25 | Connector / ODBC | Can't repeat (2288 days) | S2 | 3.51 | Windows | Any | Connector/ODBC 3.51.30 didn't support UTF8? |
| 83417 | 2016-10-17 22:56 | 2016-10-19 20:53 | MySQL Server: DML | Can't repeat (2743 days) | S3 | 5.5.52 | Ubuntu (14.04) | Any | After updating from 5.5.50 to 5.5.52 We now get Error 1300 with LOCAL INFILE |
| 42931 | 2009-02-17 13:06 | 2013-04-16 7:19 | Connector / J | Can't repeat (4025 days) | S2 | 1.1.12 | Windows (5.1 2600) | Any | cannot migrate from MS Access database |
| 40026 | 2008-10-14 16:20 | 2008-10-14 20:37 | MySQL Server: DDL | Can't repeat (5670 days) | S2 | 5.1.26 | Any | Any | CREATE INDEX not online when using utf8 columns |
| 24323 | 2006-11-14 23:10 | 2007-01-03 13:35 | MySQL Server | Can't repeat (6320 days) | S2 | 5.0.26 | Linux (Linux ) | Any | UTF8 table data converted as latin1 data when sent to client |
| 102806 | 2021-03-03 22:16 | 2021-03-05 13:59 | MySQL Server: Command-line Clients | Closed (1145 days) | S3 | 8.0.23 | Linux | Any | Linux client does not accept umlauts if started with default-character-set=utf8 |
| 101346 | 2020-10-27 16:05 | 2021-11-25 7:49 | MySQL Server: Prepared statements | Closed (1271 days) | S3 | 8.0.22 | Ubuntu (18.04) | x86 | "Illegal mix of collations" errors when matching ascii field and unicode |
| 93626 | 2018-12-15 21:22 | 2019-01-30 15:14 | MySQL Server: Charsets | Closed (1910 days) | S3 | 8.0.11 | Any | Any | Unicode string incorrectly marked as invalid |
| 79597 | 2015-12-10 19:47 | 2018-05-17 16:15 | MySQL Server: Charsets | Closed (2168 days) | S3 | 5.6.24, 5.7.10 | Any | Any | "load data infile" is limited to ASCII characters as field enclosers |
| 77105 | 2015-05-20 13:37 | 2018-04-06 8:11 | MySQL Server | Closed (2209 days) | S3 | 5.6.22 | Linux | Any | Lost data after ALTER TABLE with CHARACTER SET utf8 |
| 68366 | 2013-02-13 16:03 | 2018-01-18 13:19 | MySQL Server: Charsets | Closed (2287 days) | S5 | 5.5.29-0ubuntu0.12.10.1-log for debian- | Linux (Ubuntu 12.10) | Any | regression: >=mysql-5.4 utf8 collations are marked as not ascii compatible |
| 38720 | 2008-08-11 14:07 | 2018-01-18 13:11 | MySQL Server: Charsets | Closed (2287 days) | S2 | 5.0, 5.1, 6.0 bzr | Linux (Etch 4.0(am64 and x86)) | Any | SELECT DISTINCT on multiple attributes containing spaces in UTF8 are slow. |
| 84341 | 2016-12-26 19:45 | 2017-02-10 14:52 | MySQL Server: Documentation | Closed (2629 days) | S3 | 5.6 | Windows (7) | Any | MySQL utf8.xml missing in share\charset |
| 80631 | 2016-03-07 8:01 | 2016-10-14 16:02 | Connector / J | Closed (2778 days) | S2 | 5.1.38, 5.1.39, 6.0.3 | Any | Any | ResultSet.getString return garbled result with json type data |
| 78340 | 2015-09-05 15:53 | 2015-10-09 14:41 | MySQL Server: Documentation | Closed (3119 days) | S3 | 5.7 | Any | Any | Downgrade advice for unicode not correct |
| 78348 | 2015-09-06 9:09 | 2015-09-07 7:38 | MySQL Server: Command-line Clients | Closed (3151 days) | S3 | 5.7.8 | Any | Any | mysqlpump support for 4-byte UTF-8 |
| 71964 | 2014-03-07 9:02 | 2015-08-13 17:38 | MySQL Server: Documentation | Closed (3176 days) | S3 | 5.6.16 | Any | Any | Explanation of InnoDB physical row structure for CHAR is not clear. |
| 76237 | 2015-03-10 9:21 | 2016-06-20 16:49 | MySQL Server: Charsets | Closed (3294 days) | S3 | 5.7.5, 5.7.6, 5.7.7 | Linux (CentOS 6.5) | Any | LOAD DATA INFILE ignores a specific row silently under Db Charset is utf8 |
| 71995 | 2014-03-10 15:56 | 2014-03-31 13:36 | MySQL Server: Charsets | Closed (3676 days) | S2 | 5.5.36, 5.5.37 | Windows (Win7, 64 bit, FreeBSD 9.2) | Any | LDML collation size is limited |
| 68984 | 2013-04-17 12:19 | 2013-06-26 7:24 | MySQL Workbench: Modeling | Closed (3954 days) | S1 | 5.2.47 | MacOS (10.6.8) | Any | Crash when using a long multi-byte chars in the comments of model |
| 64205 | 2012-02-02 5:21 | 2012-05-25 20:43 | Connector / J | Closed (4351 days) | S3 | 5.1.18 | Any | Any | Connected through Connector/J 5.1 to MySQL 5.5, the error message is garbled. |
| 62333 | 2011-09-02 16:53 | 2011-09-13 15:07 | MySQL Workbench: SQL Editor | Closed (4606 days) | S3 | 5.2.33 | Windows (7 ultimate) | Any | Query browser doesn't display utf8 |
| 61483 | 2011-06-10 16:59 | 2011-06-10 18:01 | Connector / J | Closed (4701 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 |
| 58069 | 2010-11-09 7:20 | 2011-05-03 0:46 | MySQL Server: General | Closed (4739 days) | S1 | 5.0.92,5.1.53, 5.1.54, 5.5.8 | Linux (FC13 x64) | Any | LOAD DATA INFILE: valgrind reports invalid memory reads and writes with utf8 |
| 31555 | 2007-10-12 8:07 | 2011-02-16 23:43 | MySQL Server: Charsets | Closed (5055 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 |
| 45904 | 2009-07-02 10:43 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5153 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 (5295 days) | S3 | ALL | Any (Mac OS X 10.6) | Any | Wrong table format when using UTF8 strings |
| 43055 | 2009-02-20 11:50 | 2011-02-16 23:43 | MySQL Server: Charsets | Closed (5541 days) | S2 | 5.0.32 | Any | Any | Connector/J causes data truncation error when inserting into latin1 text column |
| Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
