| Showing all 6 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 43052 | 2009-02-20 9:49 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5705 days) | S3 | 5.1.30-community, 4.1, 5.0, 5.1, 6.0 bzr | Any (MS Windows XP, Linux) | Any | not optimalised (sub)query, = versus IN |
| 78497 | 2015-09-21 8:44 | 2015-09-21 9:11 | MySQL Server: DML | Verified (3301 days) | S3 | 5.6, 5.6.26, 5.6.28, 5.7.10 | Ubuntu | Any | Large select with nested subqueries return 0 rows |
| 77191 | 2015-05-29 9:14 | 2015-05-29 11:30 | MySQL Server: Optimizer | Verified (3416 days) | S2 | 5.6.21, 5.6.24, 5.7.8 | Any | Any | Subquery on information_schema including an IN clause, does not return results |
| 86930 | 2017-07-04 13:31 | 2017-07-11 19:14 | MySQL Server: Information schema | Verified (2649 days) | S3 | 5.6.29, 5.7.18 | Any | Any | Wrong results for queries with row constructors and information_schema |
| 106533 | 2022-02-22 2:05 | 2022-02-25 13:52 | MySQL Server: DML | Verified (955 days) | S3 | 8.0.25, 5.7,8.0 | Any (rhel 7.4) | Any | The time type cannot be handled in the `in` statement |
| 106597 | 2022-02-28 13:25 | 2022-03-01 7:21 | MySQL Server: DML | Verified (948 days) | S3 | 8.0.25, 8.0.28 | Any | Any | TIME type truncate error in 'in' function |
| Showing all 6 (Edit, Save, CSV, Feed) |
