| Showing 1-30 of 11245 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119701 | 2026-01-16 7:18 | 2026-01-16 9:45 | MySQL Server: Optimizer | Verified | S3 | 8.0.44 | Any | Any | after changing FLOOR function,col_1’s value unexpectedly change |
| 119700 | 2026-01-16 7:14 | 2026-01-16 9:32 | MySQL Server: Optimizer | Verified | S3 | 8.0.44 | Any | Any | column value unexpectedly change after adding distinct |
| 119698 | 2026-01-16 7:08 | 2026-01-16 9:16 | MySQL Server: Optimizer | Verified | S3 | 8.0. | Any | Any | rows become less unexpectedly caused by on clause |
| 119697 | 2026-01-16 7:06 | 2026-01-16 9:06 | MySQL Server: Optimizer | Verified | S3 | 8.0.44 | Any | Any | Bit value changed after adding DISTINCT in query |
| 119696 | 2026-01-16 7:03 | 2026-01-16 8:58 | MySQL Server: Optimizer | Verified | 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 | 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 | 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 | 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 | 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 (1 day) | 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 (1 day) | 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 (1 day) | 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 (1 day) | 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 (1 day) | 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 (1 day) | 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 (1 day) | 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 (3 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 (3 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 (3 days) | S3 | 8.0.41 | Any | Any | YEAR column IN (1,2) does not match expected conversion behavior |
| 119663 | 2026-01-13 4:24 | 2026-01-13 7:46 | MySQL Server: Optimizer | Verified (3 days) | S3 | 9.3.0 | Ubuntu | Any | Query reports error when turn on optimizer_switch |
| 119650 | 2026-01-09 2:04 | 2026-01-09 7:34 | MySQL Server: Optimizer | Verified (7 days) | S1 | 9.5.0 | Any | Any | IN operator returns unexpected result when one of values in the list is NULL |
| 119646 | 2026-01-08 7:46 | 2026-01-08 10:30 | MySQL Server: Optimizer | Verified (8 days) | S2 | 8.0.33 | Ubuntu (22.04) | Any | View + Type Conversion + IN Subquery Returns Wrong Result |
| 119639 | 2026-01-07 9:05 | 2026-01-07 10:42 | MySQL Server: Optimizer | Verified (9 days) | S2 | 8.0.42 | Any | Any | Assertion Failure in LEAST() Function with Unsigned Columns |
| 119638 | 2026-01-07 8:40 | 2026-01-07 9:59 | MySQL Server: Optimizer | Verified (9 days) | S3 | 8.0.42 | Any | Any | Incorrect Condition Evaluation for BETWEEN with NULL Upper Bound |
| 119636 | 2026-01-07 7:55 | 2026-01-07 9:20 | MySQL Server: Optimizer | Verified (9 days) | S3 | 8.0 | Any | Any | Incorrect Condition Evaluation for float unsigned zerofill Columns |
| 119635 | 2026-01-07 7:27 | 2026-01-07 11:07 | MySQL Server: Optimizer | Verified (9 days) | S3 | 8.0.42+ | Any | Any | Returns incorrect query results when using the between keyword |
| 119631 | 2026-01-06 12:13 | 2026-01-07 8:46 | MySQL Server: Optimizer | Verified (9 days) | S2 | 8.0.33 | Any (22.04) | Any | CTE with type conversion and WHERE condition in IN/EXISTS subquery returns all rows instead of filtered rows |
| 119630 | 2026-01-06 7:59 | 2026-01-07 8:28 | MySQL Server: Optimizer | Verified (9 days) | S2 | 8.0.33 | Any (22.04) | Any | Optimizer incorrectly merges derived table with type conversion and WHERE clause, causing wrong query results |
| 119621 | 2026-01-05 11:11 | 2026-01-05 15:05 | MySQL Server: JSON | Verified (11 days) | S2 | 8.0.43 | Any | Any | query on partitioned table report "the JSON binary value contains invalid data" |
| 119619 | 2026-01-04 14:07 | 2026-01-04 21:17 | MySQL Server: Optimizer | Verified (12 days) | S1 | 8.0 | Any | Any | Incorrect results for REPLACE function |
| Showing 1-30 of 11245 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
