« Show Previous 30 Entries | Showing 31-60 of 308 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
96361 | 2019-07-29 8:39 | 2020-03-31 13:39 | MySQL Server: Optimizer | Duplicate (1737 days) | S3 | 8.0.17 | Windows | Any | Request with empty date |
97461 | 2019-11-03 14:51 | 2019-11-05 13:09 | MySQL Server: Optimizer | Duplicate (1638 days) | S3 | 8.0.14+ | Any | Any | Wrapping `select (value)` with `select * from` gives wrong result |
97486 | 2019-11-05 3:53 | 2019-11-06 15:37 | MySQL Server: Optimizer | Duplicate (1637 days) | S3 | 8.0.17 | Windows (10) | x86 (x64) | mysql8.0 If the select SQL query statement is too long, the bit result will be w |
98287 | 2020-01-19 22:17 | 2020-01-21 12:54 | MySQL Server: Optimizer | Duplicate (1562 days) | S3 | 8.0.19 | Any | Any | Explanation of hash joins is inconsistent across EXPLAIN formats |
98825 | 2020-03-04 7:58 | 2020-03-06 9:26 | MySQL Server: Optimizer | Duplicate (1516 days) | S2 | mysql-8.0.18, 8.0.19 | Any | Any | sum() function result may be error in select query |
99913 | 2020-06-17 11:00 | 2020-06-19 12:37 | MySQL Server: Optimizer | Duplicate (1411 days) | S2 | 8.0.20 | Windows | Any | Group by corrupts data |
100253 | 2020-07-18 1:47 | 2021-11-05 8:47 | MySQL Server: Optimizer | Duplicate (930 days) | S2 | 8.0.21, 8.0.13 | Any | Any | Skip Scan retrieves incorrect Result |
101198 | 2020-10-15 20:22 | 2020-10-17 16:18 | MySQL Server: Optimizer | Duplicate (1291 days) | S3 | 8.0 | Any | Any | SET_VAR optimizer hint doesn't recognize value that has decimal point |
101269 | 2020-10-22 3:26 | 2022-04-11 9:06 | MySQL Server: Optimizer | Duplicate (750 days) | S1 | 5.7, 8.0, 8.0.22, 5.7.32 | Any | Any | using different index may produce different results |
101430 | 2020-11-03 9:11 | 2021-07-23 13:25 | MySQL Server: Optimizer | Duplicate (1261 days) | S3 | 8.0.18 | Any | Any | Invalid JSON number 2e308 in opt trace for FORCE INDEX |
101847 | 2020-12-03 7:17 | 2021-10-26 12:18 | MySQL Server: Optimizer | Duplicate (917 days) | S3 | 8.0 | Any | Any | Potentially wrong results |
101848 | 2020-12-03 7:41 | 2022-04-11 13:15 | MySQL Server: Optimizer | Duplicate (750 days) | S3 | 8.0 | Any | Any | Potentially wrong results |
102655 | 2021-02-19 3:07 | 2021-12-02 11:19 | MySQL Server: Optimizer | Duplicate (880 days) | S3 | 8.0, 8.0.23 | Any | Any | results from SELECT are different when use WHERE or not |
102792 | 2021-03-03 7:18 | 2021-03-03 8:03 | MySQL Server: Optimizer | Duplicate (1154 days) | S3 | 8.0.23 | Any (ubuntu 2004 desktop x64) | Any | analyze table didn't refresh statistics correctly in information_schema |
95411 | 2019-05-17 17:39 | 2019-05-20 10:03 | MySQL Server: Optimizer | Duplicate (1807 days) | S2 | 8.0.16 | Any | Any | LATERAL produces wrong results (values insted of NULLs) on 8.0.16 |
103346 | 2021-04-16 13:48 | 2021-06-10 4:49 | MySQL Server: Optimizer | Duplicate (1055 days) | S2 | 8.0.16, 8.0.23 | Any | Any | Mysql 8 vs 5.7 Query Regression failure |
103745 | 2021-05-20 3:55 | 2021-05-20 5:06 | MySQL Server: Optimizer | Duplicate (1076 days) | S2 | 8.0, 8.0.25 | Any | Any | incorrect output by index merge |
104000 | 2021-06-14 7:44 | 2021-09-27 13:34 | MySQL Server: Optimizer | Duplicate (1051 days) | S3 | 8.0.25 | Any | Any | RANGE OPTIMIZER MEMORY USAGE INCREASES WITH MORE SECONDARY INDEXES! |
105303 | 2021-10-22 18:55 | 2021-10-23 6:33 | MySQL Server: Optimizer | Duplicate (920 days) | S2 | 8.0.20+ | Any | Any | Unmanageable Sort Buffer Behavior in 8.0.20+ |
106063 | 2022-01-05 12:42 | 2022-01-06 14:12 | MySQL Server: Optimizer | Duplicate (845 days) | S2 | 8.0, 8.0.27 | Any | Any | Condition on aggregared expr in HAVING clause produces bad result in some cases |
106191 | 2022-01-18 5:45 | 2022-01-19 8:49 | MySQL Server: Optimizer | Duplicate (832 days) | S2 | 8.0.27 | Windows | x86 | user variable not work in where |
106328 | 2022-01-29 0:40 | 2022-02-09 1:33 | MySQL Server: Optimizer | Duplicate (811 days) | S3 | 8.0.28, 5.7.37 | Any | Any | Huge value in ORDER BY clause cause unexpected output |
106522 | 2022-02-21 2:57 | 2022-02-21 6:39 | MySQL Server: Optimizer | Duplicate (799 days) | S3 | 8.0.25 | Any | Any | 8.025 causes differences in execution results |
106611 | 2022-03-01 13:20 | 2022-03-02 11:26 | MySQL Server: Optimizer | Duplicate (790 days) | S2 | 8.0.27, 8.0.28 | Any | Any | Nested Null-Safe Equal gives wrong result |
107338 | 2022-05-19 6:10 | 2022-05-19 7:07 | MySQL Server: Optimizer | Duplicate (712 days) | S2 | 8.0.26 | MacOS | x86 | select return wrong result about time column |
107840 | 2022-07-11 21:26 | 2022-07-12 11:51 | MySQL Server: Optimizer | Duplicate (658 days) | S3 | Windows (XP SP3) | Any | MySQL 5.6.20 | |
109127 | 2022-11-17 17:53 | 2022-11-22 6:44 | MySQL Server: Optimizer | Duplicate (529 days) | S3 | 8.0.31 | Linux (Red Hat, CentOS, Kylin) | Any | skip scan retrieves incorrect result after delete |
109142 | 2022-11-18 18:59 | 2022-11-22 6:43 | MySQL Server: Optimizer | Duplicate (525 days) | S1 | 8.0.31 | Linux | Any | optimizer skip scan cause incorrect result |
8139 | 2005-01-26 7:49 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (5658 days) | S3 | 4.1.8 | Linux (Linux) | Any | subselect index not used for "in" but used for "=" |
8632 | 2005-02-20 13:11 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (7000 days) | S3 | 4.1.10 | Any | SQL_CALC_FOUND_ROWS and DUAL |
« Show Previous 30 Entries | Showing 31-60 of 308 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |