| Showing 1-30 of 11248 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119790 | 2026-01-27 10:14 | 2026-01-27 12:07 | MySQL Server: Optimizer | Verified | S1 | 8.0.44 | Any | Any | Unexpected result of expression IN NULL |
| 119780 | 2026-01-26 14:40 | 2026-01-26 15:15 | MySQL Server: Optimizer | Verified (1 day) | S3 | 8.0.44 | Ubuntu (22.04) | Any | UNION ALL + AND + WHERE IS UNKNOWN query results are incorrect |
| 119778 | 2026-01-26 12:56 | 2026-01-26 15:01 | MySQL Server: Optimizer | Verified (1 day) | S3 | 8.0.x, 8.4.x | Any | Any | after changing SUM(distinct x) to - SUM(distinct -x),the value unexpectedly change |
| 119776 | 2026-01-26 9:31 | 2026-01-26 13:51 | MySQL Server: Optimizer | Verified (1 day) | S3 | 8.0.41 | Any | Any | Semantically identical SQLs yield different result sets. |
| 119752 | 2026-01-22 15:08 | 2026-01-22 21:36 | MySQL Server: Optimizer | Verified (5 days) | S3 | 8.0.44 | Any | Any | after changing MINUTE(subq.c1) to MINUTE(subq.c1 + INTERVAL '60' MINUTE),the result become empty. |
| 119745 | 2026-01-22 10:24 | 2026-01-27 7:03 | MySQL Server: Documentation | Verified | S3 | 9.6.0 | Any | Any | documentation: mysql 9.6 release notes - classic_hashing |
| 119741 | 2026-01-22 7:00 | 2026-01-22 8:35 | MySQL Server: Optimizer | Verified (5 days) | S1 | 8.0.44 | Any | Any | internal_tmp_mem_storage_engine = MEMORY setting makes the DISTINCTROW returns incorrect result on 0 and -0 |
| 119729 | 2026-01-20 17:17 | 2026-01-23 12:08 | MySQL Server: Optimizer | Verified (6 days) | S4 | Any | Any | Add native support for UUID v7 | |
| 119727 | 2026-01-20 10:11 | 2026-01-20 11:56 | MySQL Server: Data Types | Verified (7 days) | S3 | 8.0.44 | Any | Any | wrong result for 'value between a and null' for certain temporal types |
| 119724 | 2026-01-20 5:55 | 2026-01-20 8:08 | MySQL Server: Optimizer | Verified (7 days) | S3 | 8.0.44 | Any | Any | after changing asin function in group clause,column's value unexpectedly change |
| 119716 | 2026-01-19 1:36 | 2026-01-19 9:16 | MySQL Server: Optimizer | Verified (8 days) | S1 | 8.0.44 | Any | Any | Suboptimal query plan generated by normal query compare to prepared statement |
| 119714 | 2026-01-18 12:26 | 2026-01-19 9:01 | MySQL Server: Optimizer | Verified (8 days) | S3 | 8.0.44 | Any | Any | after changing ASIN(hpg31.c1) in group clause,the col_1’s value unexpectedly change. |
| 119713 | 2026-01-18 11:19 | 2026-01-20 9:37 | MySQL Server: Optimizer | Verified (7 days) | S3 | 8.0.39, 8.0.44, 8.4.6 | Any | Any | MySQL has hard time using the right indexes |
| 119701 | 2026-01-16 7:18 | 2026-01-16 9:45 | MySQL Server: Optimizer | Verified (11 days) | S3 | 8.0.44 | Any | Any | after changing FLOOR function,col_1’s value unexpectedly change |
| 119698 | 2026-01-16 7:08 | 2026-01-16 9:16 | MySQL Server: Optimizer | Verified (11 days) | S3 | 8.0. | Any | Any | rows become less unexpectedly caused by on clause |
| 119696 | 2026-01-16 7:03 | 2026-01-16 8:58 | MySQL Server: Optimizer | Verified (11 days) | S3 | 8.0.44 | Any | Any | float value Precision loss caused by removing distinct |
| 119695 | 2026-01-16 6:59 | 2026-01-16 8:48 | MySQL Server: Optimizer | Verified (11 days) | S3 | 8.0.44 | Any | Any | The appearance of rows that should not exist caused by on clause |
| 119694 | 2026-01-16 6:56 | 2026-01-16 8:39 | MySQL Server: Optimizer | Verified (11 days) | S3 | 8.0.44 | Any | Any | rows unexpectedly become less after changing INNER to LEFT |
| 119693 | 2026-01-16 6:39 | 2026-01-16 8:28 | MySQL Server: Optimizer | Verified (11 days) | S3 | 8.0.44 | Any | Any | column value change after changing INNER to LEFT |
| 119692 | 2026-01-16 5:23 | 2026-01-16 8:09 | MySQL Server: Optimizer | Verified (11 days) | S1 | 8.0.44 | Any | Any | The normal query generated a non-optimal query plan. |
| 119687 | 2026-01-15 10:23 | 2026-01-15 13:18 | MySQL Server: Optimizer | Verified (12 days) | S1 | 8.0.44 | Any | Any | Inconsistent behaviour between normal and prepared INSERT |
| 119686 | 2026-01-15 8:37 | 2026-01-15 13:11 | MySQL Server: Optimizer | Verified (12 days) | S2 | 8.0.44 | Linux | x86 | Incorrect result when joined table has PRIMARY KEY and WHERE predicate involves CASE |
| 119684 | 2026-01-14 18:11 | 2026-01-15 9:33 | MySQL Server: Documentation | Verified (12 days) | S3 | 9.5.0 | Any | Any | 9.5.0 release notes explain the enforce_gitd_consistency change incorrectly |
| 119683 | 2026-01-14 15:35 | 2026-01-15 12:57 | MySQL Server: Optimizer | Verified (12 days) | S1 | 8.0.44 | Linux | x86 | Different results for INNER JOIN and STRAIGHT_JOIN with GREATEST() IN predicate |
| 119681 | 2026-01-14 14:19 | 2026-01-15 12:47 | MySQL Server: Optimizer | Verified (12 days) | S3 | 9.5.0 | Any | Any | Floating-point precision loss occurs when changing avg(x) to -avg(-x) |
| 119680 | 2026-01-14 13:51 | 2026-01-15 12:25 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0.44 | Any | Any | after changing AVG(cte.col_2) to -AVG(-cte.col_2) ,rows become less |
| 119679 | 2026-01-14 13:40 | 2026-01-15 11:25 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0.45 | Any | Any | after changing SUM(t3.c9) to -SUM(-t3.c9),the rows become less |
| 119670 | 2026-01-13 13:46 | 2026-01-13 14:51 | MySQL Server: Optimizer | Verified (14 days) | S1 | 8.0.44 | Any | Any | Incorrect result caused by index |
| 119669 | 2026-01-13 13:27 | 2026-01-13 14:53 | MySQL Server: Optimizer | Verified (14 days) | S1 | 8.0.44 | Any | Any | Inconsistent behaviour between normal query and prepared statement |
| 119666 | 2026-01-13 7:37 | 2026-01-13 8:16 | MySQL Server: Optimizer | Verified (14 days) | S3 | 8.0.41 | Any | Any | YEAR column IN (1,2) does not match expected conversion behavior |
| Showing 1-30 of 11248 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
