| Showing 1-30 of 7279 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 111397 | 2023-06-13 13:32 | 2023-06-14 8:30 | MySQL Server: Optimizer | Verified (310 days) | S3 | 8.0 | Any | Any | 表达式进行<=>比较并将结果进行与操作，执行结果错误 |
| 113585 | 2024-01-09 1:41 | 2024-01-09 7:25 | Connector / NET | Verified (100 days) | S3 | 8.2.0 | Any | Any | 并发多个连接时报错 System.NotSupportedException: MySQL Connector/NET does not currently s |
| 114255 | 2024-03-07 7:29 | 2024-03-13 11:50 | MySQL Server: Installing | Verified (37 days) | S3 | 8.0.34/35 | Linux | ARM (el8) | 安装社区版8.0.34/35glibc2.28-arm版本报错:ELF load command alignment not page-aligned |
| 105855 | 2021-12-10 5:22 | 2021-12-10 6:28 | MySQL Workbench | Verified (860 days) | S2 | 8.0.27 | MacOS (macOS 11.2.x Big Sur x86_64) | Any | 同步模型时JSON字段未正确识别 |
| 110242 | 2023-02-28 23:56 | 2024-01-22 9:15 | Connector / J | Analyzing (412 days) | S2 | 8.0.32 | Any | Any | zeroDateTimeBehavior=CONVERT_TO_NULL should apply to TIMSTAMP when date is zero |
| 72672 | 2014-05-16 18:17 | 2014-05-22 9:21 | MySQL Server: Data Types | Verified (3619 days) | S2 | 5.5.31,5.5.34, 5.7.5, 5.6.19 | Any | Any | Zero-valued DATETIME column can be simultaneously NULL and NOT NULL |
| 59526 | 2011-01-15 14:08 | 2018-09-09 20:45 | MySQL Server: DML | Verified (4826 days) | S3 | 5.0, 5.1, 5.6.2 | Any | Any | ZERO-date can be inserted in 'no_zero_date' sql_mode |
| 95416 | 2019-05-20 0:33 | 2019-05-22 21:45 | MySQL Server: Optimizer | Verified (1795 days) | S2 | 5.7.25,8.0.15, 5.6.44, 5.7.26, 8.0.16 | Any | Any | ZERO Date is both NULL and NOT NULL |
| 79345 | 2015-11-19 17:54 | 2018-04-29 21:31 | MySQL Utilities | Verified (2181 days) | S2 | CentOS (6) | Any | Yum install of mysql-utilities-1.5.6-1.el6.src.rpm fails | |
| 113026 | 2023-11-09 14:47 | 2024-01-22 4:45 | MySQL Operator | Verified (146 days) | S1 | Linux | ARM | Your operator cannot adapt to multiple architectures | |
| 7742 | 2005-01-08 11:06 | 2017-11-11 20:47 | MySQL Server: DML | Verified (3753 days) | S3 | 4.1 + | Linux (Linux Red Hat 9) | Any | You can't reinvoke the same Temporary Table more than once. |
| 90089 | 2018-03-15 12:57 | 2018-03-15 17:36 | MySQL Server: DML | Verified (2226 days) | S2 | 5.5/5.6/5.7/8.0 | Linux | Any | Year type column have index , between operate sql , the result is wrong . |
| 92688 | 2018-10-05 13:38 | 2018-10-06 12:22 | MySQL Connectors: Document Store: DevAPI | Verified (2021 days) | S3 | 8.0.13 | Linux | Any | Year field in document returns error when used |
| 80367 | 2016-02-15 10:37 | 2017-03-09 16:25 | MySQL Server: XML functions | Verified (2985 days) | S2 | 5.6, 5.7 | Any | Any | XML parser fail parse processing instruction |
| 92491 | 2018-09-19 7:07 | 2019-10-03 12:00 | MySQL Workbench: SQL Editor | Verified (2038 days) | S3 | 8.0.12, 8.0.17 | Windows | x86 | XML export does not encoded ampersand, less-than, or double-quote characgters |
| 84441 | 2017-01-09 4:12 | 2017-01-31 5:18 | MySQL Utilities: Binlog Events | Verified (2634 days) | S3 | 5.7.15 | Any | Any | Xids for DDL are not logged in the binlog |
| 93948 | 2019-01-16 8:23 | 2019-02-08 4:52 | MySQL Server: Replication | Verified (1896 days) | S3 | 8.0.13 | Any | Any | XID inconsistency on master-slave with CTAS |
| 109668 | 2023-01-17 21:56 | 2024-01-26 6:08 | MySQL Server: Group Replication | Verified (311 days) | S2 | 8.0.27, 8.0.33 | CentOS | x86 | XCom connection stalled forever in read() syscall over network |
| 62693 | 2011-10-12 7:04 | 2022-09-04 20:45 | Connector / J | Verified (4011 days) | S3 | 5.1.18 | Any | Any | XAConnection savepoint capability |
| 17343 | 2006-02-13 17:23 | 2018-09-09 20:45 | MySQL Server: General | Verified (6259 days) | S2 | 5.0.19-BK | Linux (Linux, Windows XP) | Any | XAConnection doesn't allow second XA START |
| 102992 | 2021-03-15 23:57 | 2021-03-25 12:22 | MySQL Server: Replication | Verified (1120 days) | S3 | 5.7, 8.0, 5.7.33 | Any | Any | XA transactions do not update slave_relay_log_info table |
| 109434 | 2022-12-20 7:52 | 2023-01-09 12:38 | MySQL Server: XA transactions | Verified (479 days) | S3 | 8.0 | Any | Any | Xa transaction recovery issue after mysql restarts after crash |
| 98616 | 2020-02-15 15:20 | 2021-01-05 9:50 | MySQL Server: XA transactions | Verified (1517 days) | S3 | 5.7.29 | Any | Any | XA PREPARE/XA COMMIT/XA ROLLBACK lost if mysql crash just after binlog flush |
| 99205 | 2020-04-08 1:36 | 2020-04-08 11:19 | MySQL Server: XA transactions | Verified (1471 days) | S2 | 8.0.18, 8.0.19 | Any | Any | xa prepare write binlog while execute failed |
| 87560 | 2017-08-28 9:14 | 2021-04-19 4:25 | MySQL Server: XA transactions | Verified (2318 days) | S2 | mysql-5.7.17 | Any | Any | XA PREPARE log order error in replication and binlog recovery |
| 76233 | 2015-03-09 20:10 | 2020-02-13 8:24 | MySQL Server: Replication | Verified | S3 | 5.7.7 | Any | Any | XA prepare is logged ahead of engine prepare |
| 102661 | 2021-02-19 11:20 | 2021-02-19 12:17 | MySQL Server: XA transactions | Verified (1154 days) | S3 | 8.0.22, 8.0.23, 5.7.33 | Any | Any | xa prepare failed lead replication error |
| 88534 | 2017-11-17 11:04 | 2021-03-23 8:17 | MySQL Server: XA transactions | Verified (1122 days) | S1 | 5.7, 5.7.20 | Any | Any | XA may lost prepared transaction and cause different between master and slave. |
| 89860 | 2018-03-01 1:34 | 2018-05-31 7:36 | MySQL Server: XA transactions | Verified (2149 days) | S2 | 5.7, 5.7.21 | Any | Any | XA may lost prepared transaction and cause different between master and slave. |
| 72036 | 2014-03-14 2:41 | 2022-09-04 20:45 | Connector / J | Verified | S3 | Any | Any | XA isSameRM() shouldn't take database into account |
| Showing 1-30 of 7279 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
