Showing 1-30 of 33 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
47295 | 2009-09-13 14:00 | 2010-01-04 14:29 | MySQL Server: Locking | Not a Bug (5397 days) | S3 | 5.1.31-1ubuntu2 | Any | Any | Locked a record that shouldn't be such |
49991 | 2009-12-30 13:14 | 2015-02-24 9:27 | MySQL Server: Stored Routines | Closed (3520 days) | S3 | 5.0.85 | MacOS | Any | Multiple assignments cause exit from a cursor loop in stored procedures |
70333 | 2013-09-13 14:15 | 2013-10-11 16:15 | MySQL Server: FULLTEXT search | Closed (4021 days) | S3 | 5.6.13 | Any | Any | InnoDB Fulltext search doesn't find records when savepoints are involved |
70337 | 2013-09-13 16:05 | 2013-09-13 23:59 | MySQL Server | Not a Bug (4049 days) | S3 | 5.6.13 | Any | Any | SELECT returning inappopriate results |
71816 | 2014-02-24 13:12 | 2014-06-16 14:50 | MySQL Server: Documentation | Closed (3773 days) | S1 | 5.6.16 | Any | Any | InnoDB Fulltext search doesn't find records when savepoints are involved (2) |
74553 | 2014-10-24 16:48 | 2015-02-10 12:19 | MySQL Server | Closed (3534 days) | S1 | 5.6.21 | Linux | Any | Crash when starting MySQL 5.6.21, using data from 5.6.20 |
76022 | 2015-02-24 9:46 | 2015-09-14 11:12 | MySQL Server: InnoDB storage engine | Not a Bug (3519 days) | S3 | 5.6.20 | Linux | Any | Wrong row format reported on an InnoDB table |
76227 | 2015-03-09 13:28 | 2015-03-11 19:40 | MySQL Server: InnoDB storage engine | Not a Bug (3505 days) | S3 | 5.6.23 | Any | Any | FKs are checked in some cases, even if FOREIGN_KEY_CHECK = 1 |
76585 | 2015-04-03 10:07 | 2018-02-19 14:36 | MySQL Server | Closed (2429 days) | S3 | 5.6.27, 5.7.21 | Any | Any | Runtime changes to `long_query_time` are ignored. |
79675 | 2015-12-16 16:48 | 2019-06-28 19:42 | MySQL Server: Optimizer | Closed (2705 days) | S1 | 5.7/8.0 | Any | Any | index_merge_intersection optimization causes wrong query results |
79677 | 2015-12-16 17:49 | 2015-12-17 13:47 | MySQL Server: Optimizer | Verified (3224 days) | S3 | 5.6.27, 5.6.28 | Any | Any | Optimizer performs a significantly wrong plan |
81247 | 2016-04-29 16:06 | 2016-05-02 6:47 | MySQL Server: mysqlpump Command-line Client | Verified (3087 days) | S3 | 5.7.10 | Any | Any | mysqlpump incorrectly dumps triggers |
81272 | 2016-05-02 7:29 | 2016-05-02 7:47 | MySQL Server: Documentation | Duplicate (3087 days) | S3 | 5.7.11 | Any | Any | NUMA interleave is incorrectly displayed as parameter in the documentation |
81365 | 2016-05-10 13:07 | 2018-01-31 15:03 | MySQL Server: mysqlpump Command-line Client | Verified (3078 days) | S3 | 5.7.*, 5.7.12 | Any | Any | mysqlpump always includes the schema name and statements,even in single-db dumps |
84375 | 2016-12-30 10:27 | 2017-08-02 14:26 | MySQL Server: Documentation | Closed (2630 days) | S1 | 5.7.17 | Any | Any | Changing MASTER_DELAY to 0 purges the relay log, causing corruption. |
84605 | 2017-01-23 8:36 | 2019-08-29 14:15 | MySQL Server: Documentation | Closed (2806 days) | S3 | Any | Any | `innodb_data_home_dir` has inconsistent handling, or documentation | |
88230 | 2017-10-26 9:15 | 2017-12-08 11:34 | MySQL Server: JSON | Closed (2519 days) | S3 | 5.7.18 | Any | Any | MySQL normalizes decimal numbers with zero fractional part to integers |
98091 | 2019-12-29 15:01 | 2020-10-20 12:34 | MySQL Server: InnoDB storage engine | Closed (1455 days) | S3 | 8.0.18, 5.7.29, 8.0.19 | Linux | x86 | InnoDB does not initialize raw disk partitions |
98212 | 2020-01-13 22:20 | 2020-08-27 12:41 | MySQL Server: Documentation | Closed (1509 days) | S3 | 8.0.18 | Any | Any | Incomplete documentation of `innodb_data_file_path` |
98279 | 2020-01-17 22:49 | 2020-01-20 16:07 | MySQL Server: Optimizer | Not a Bug (1729 days) | S3 | 8.0.16 | Any | Any | Skip Scan Range Optimization is not applied on temporary tables |
98287 | 2020-01-19 22:17 | 2020-01-21 12:54 | MySQL Server: Optimizer | Duplicate (1729 days) | S3 | 8.0.19 | Any | Any | Explanation of hash joins is inconsistent across EXPLAIN formats |
98704 | 2020-02-21 8:34 | 2020-02-26 13:29 | MySQL Server | Not a Bug (1692 days) | S3 | 8.0.15 | Linux | Any | Assertion failure on too many open files error |
98881 | 2020-03-09 15:43 | 2020-03-13 13:59 | MySQL Server: Documentation | Closed (1676 days) | S4 | 8.0.x | Any | Any | CTE manpage doesn't mention SET_VAR |
98896 | 2020-03-10 18:22 | 2020-04-21 17:30 | MySQL Server: DDL | Closed (1637 days) | S3 | 8.0.19 | Any | Any | CREATE TABLE ... SELECT fails if there is a functional index |
98925 | 2020-03-12 11:16 | 2020-05-21 14:27 | MySQL Server: DML | Closed (1607 days) | S3 | 8.0.19 | Any | Any | LOAD DATA INFILE fails if there is a functional index |
98937 | 2020-03-12 16:06 | 2023-12-15 12:02 | MySQL Server: Optimizer | Verified (1676 days) | S4 | 8.0 | Any | Any | Functional indexes prevent JOINs to use them |
100003 | 2020-06-26 11:18 | 2020-06-29 8:29 | MySQL Server: Security: Privileges | Verified (1568 days) | S3 | 8.0.20, 5.7.30 | Any | Any | EXPLAIN FOR CONNECTION seems to still require the SUPER privilege |
100046 | 2020-06-30 9:43 | 2020-06-30 13:00 | MySQL Server: Optimizer | Not a Bug (1567 days) | S3 | 8.0.20 | Any | Any | Very slow plan with combination of OR+noncorrelated subqueries+ORDER BY+LIMIT |
103225 | 2021-04-06 15:03 | 2022-06-21 11:58 | MySQL Server: Optimizer | Closed (1074 days) | S3 | 8.0 | Ubuntu | Any | "Out of sort memory error" has an inconsistent relationship with the buffer size |
104899 | 2021-09-10 7:33 | 2022-06-22 0:31 | MySQL Server: DDL | Verified (1130 days) | S2 | 8.0.25, 8.0.26, 8.0.13 | Any | Any | ALTER TABLE ALGORITHM=INSTANT fails if there *was* a fulltext index |
Showing 1-30 of 33 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |