Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
64634 | 2012-03-13 13:11 | 2012-04-01 10:56 | MySQL Server: Optimizer | Verified (4379 days) | S3 | 5.6.4-m7 | Any | Any | No result when binding to same field with different trailing spaces |
78348 | 2015-09-06 9:09 | 2015-09-07 7:38 | MySQL Server: Command-line Clients | Closed (3125 days) | S3 | 5.7.8 | Any | Any | mysqlpump support for 4-byte UTF-8 |
74817 | 2014-11-12 13:22 | 2014-11-13 6:25 | MySQL Server: Charsets | Verified (3423 days) | S3 | 5.6.15, 5.6.21 | Windows (Windows 7) | Any | Character set issue with view |
74816 | 2014-11-12 12:28 | 2015-08-17 16:45 | MySQL Server: DDL | Verified (3423 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 |
74701 | 2014-11-05 16:25 | 2014-11-06 6:57 | MySQL Server: Charsets | Verified (3430 days) | S3 | 5.6.21 | Any | Any | CONVERT TO CHARACTER SET combined with MODIFY COLUMN leads to unexpected results |
71964 | 2014-03-07 9:02 | 2015-08-13 17:38 | MySQL Server: Documentation | Closed (3150 days) | S3 | 5.6.16 | Any | Any | Explanation of InnoDB physical row structure for CHAR is not clear. |
71995 | 2014-03-10 15:56 | 2014-03-31 13:36 | MySQL Server: Charsets | Closed (3650 days) | S2 | 5.5.36, 5.5.37 | Windows (Win7, 64 bit, FreeBSD 9.2) | Any | LDML collation size is limited |
71778 | 2014-02-20 11:03 | 2014-02-20 11:09 | MySQL Server: Charsets | Not a Bug (3689 days) | S3 | 5.6 | Any | Any | latin1 accepts characters from cp1252 (as 0x92) but can't convert them to utf8 |
42931 | 2009-02-17 13:06 | 2013-04-16 7:19 | Connector / J | Can't repeat (3999 days) | S2 | 1.1.12 | Windows (5.1 2600) | Any | cannot migrate from MS Access database |
68984 | 2013-04-17 12:19 | 2013-06-26 7:24 | MySQL Workbench: Modeling | Closed (3928 days) | S1 | 5.2.47 | MacOS (10.6.8) | Any | Crash when using a long multi-byte chars in the comments of model |
68375 | 2013-02-14 9:46 | 2013-02-15 15:43 | MySQL Server: Charsets | Not a Bug (4059 days) | S3 | 5.1.68 | Linux (x86_64-glibc23) | Any | Certain unicode characters cause false positives when matching strings |
55606 | 2010-07-28 15:25 | 2015-08-30 17:21 | MySQL Server: Charsets | Verified (3976 days) | S5 | 5.1.47, 5.1.50-bzr, 5.5.23, 5.6.11 | Linux | Any | Charset on ENUMS influencing performance too much |
79397 | 2015-11-24 12:00 | 2015-11-24 12:20 | MySQL Workbench: Modeling | Duplicate (3047 days) | S3 | 6.3.5 | Windows (Windows 8.1) | Any | collation not rekognized |
66932 | 2012-09-23 13:32 | 2012-09-23 23:56 | MySQL Server: Charsets | Verified (4204 days) | S3 | 5.5.25a | Linux | Any | GREATEST produces invalid result if in subquery with utf8_hungarian_ci collation |
66480 | 2012-08-21 9:04 | 2018-11-24 8:37 | MySQL Server: Data Types | Verified (4237 days) | S3 | 5.5.27, 5.5.28 | Any (Squeeze) | Any | Myql comparison of curtime() with a constant in utf8 |
64354 | 2012-02-16 15:45 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (4424 days) | S1 | 7.2.4 GA | Any | Any | LIKE function does not work in MySQL Cluster 7.2.4 for UTF8 char/varchar fields |
65368 | 2012-05-18 21:27 | 2013-01-20 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4086 days) | S2 | 5.5.20 | MacOS | Any | Japanese characters utf8 bin collide when they should not |
65233 | 2012-05-07 21:34 | 2013-02-06 8:50 | MySQL Server: FULLTEXT search | Duplicate (4112 days) | S1 | 5.6.5-m8-log | Linux (Linux 2.6.18-194.32.1.el5) | Any | Using percent sign in FTS crashes the server |
64006 | 2012-01-12 9:32 | 2012-01-13 11:26 | Connector / J | Not a Bug (4458 days) | S2 | 5.1.14 | Windows | Any | Not able to insert Norwegian characters from Java Application |
63829 | 2011-12-21 19:34 | 2020-04-27 17:55 | MySQL Server: DML | Verified (4480 days) | S3 | 5.1.58, 5.5.20 | Any | Any | Search containig backslash doesn't work if field collation is utf8_unicode_ci |
64578 | 2012-03-07 7:59 | 2012-07-06 15:34 | MySQL Server: Charsets | Not a Bug (4283 days) | S3 | 5.1.59-community-log, 5.1.63, 5.5.23, 5.6.6 | Any | Any | UTF8 is not UTF8 ? |
64205 | 2012-02-02 5:21 | 2012-05-25 20:43 | Connector / J | Closed (4325 days) | S3 | 5.1.18 | Any | Any | Connected through Connector/J 5.1 to MySQL 5.5, the error message is garbled. |
62945 | 2011-10-26 15:47 | 2012-07-06 15:37 | MySQL Server: Charsets | Not a Bug (4283 days) | S3 | 5.5.15 | Any (7, x64) | Any | Like not work correctly for slovakian collate |
62442 | 2011-09-15 11:50 | 2011-09-16 20:03 | MySQL Server: Charsets | Not a Bug (4577 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)) |
68366 | 2013-02-13 16:03 | 2018-01-18 13:19 | MySQL Server: Charsets | Closed (2261 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 |
83461 | 2016-10-20 12:59 | 2023-01-11 8:15 | MySQL Server: Replication | Can't repeat (442 days) | S3 | 8.0.0, 8.0.18, 5.7.28 | Any | Any | replication breakage noted from 5.7.10 to 8.0.0 |
80535 | 2016-02-26 19:46 | 2022-05-09 22:07 | Connector / Python | Duplicate (2390 days) | S2 | 2.1.3 | Any | Any | _batch_insert uses mysql encoding instead of python encoding & fails w/ utf8mb4 |
105077 | 2021-09-29 15:31 | 2021-10-07 13:41 | MySQL Server: Charsets | Not a Bug (910 days) | S3 | 8.0.26 | Any | Any | As of 8.0.26, mysqldump substitutes utf8mb3 for utf8 |
106389 | 2022-02-07 5:44 | 2022-02-07 6:10 | MySQL Server: Charsets | Verified (780 days) | S3 | 8.0 | Any (N/A) | Any | What is the next step in making utf8 and utf8mb4 synonyms? |
102806 | 2021-03-03 22:16 | 2021-03-05 13:59 | MySQL Server: Command-line Clients | Closed (1119 days) | S3 | 8.0.23 | Linux | Any | Linux client does not accept umlauts if started with default-character-set=utf8 |
Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |