Showing all 9 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
110825 | 2023-04-26 23:58 | 2023-04-27 8:29 | MySQL Server: Charsets | Verified (593 days) | S3 | 8.0.32 | Any | Any | Explicit COLLATE clause output in SHOW CREATE TABLE incorrectly |
104984 | 2021-09-18 11:21 | 2021-09-22 6:23 | MySQL Server: Data Dictionary | Verified (1175 days) | S2 | 8.0.23, 8.0.26 | CentOS | x86 | Failed to upgrade to mysql 8.0 because of the character set of the field comment |
103918 | 2021-06-05 13:58 | 2021-06-08 8:34 | MySQL Server: DML | Verified (1281 days) | S3 | 8.0.25, 5.7.34 | Any | Any | Illegal mix of collations |
100885 | 2020-09-18 3:43 | 2020-11-09 11:38 | MySQL Server: JSON | Verified (1544 days) | S5 | 5.7.31 | Any | Any | generated column index against json column is not used with different encoding |
73967 | 2014-09-18 12:35 | 2015-07-20 8:17 | MySQL Server: Performance Schema | Verified (3619 days) | S3 | 5.6.20 | Any | Any | Incorrect string value for sql_text |
75203 | 2014-12-13 14:45 | 2014-12-15 11:44 | MySQL Server: Replication | Verified (3648 days) | S3 | 5.7.5-m15 | Any | Any | Misleading error when binlog name contains 4 byte utf8 on chaning to table |
74816 | 2014-11-12 12:28 | 2015-08-17 16:45 | MySQL Server: DDL | Verified (3680 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 |
74817 | 2014-11-12 13:22 | 2014-11-13 6:25 | MySQL Server: Charsets | Verified (3680 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 (3687 days) | S3 | 5.6.21 | Any | Any | CONVERT TO CHARACTER SET combined with MODIFY COLUMN leads to unexpected results |
Showing all 9 (Edit, Save, CSV, Feed) |