| Showing 1-30 of 14944 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119738 | 2026-01-22 4:12 | 2026-01-22 8:20 | MySQL Server: Components / Services | Open | S2 | 8.4.8 | MacOS (26.2) | ARM | global-buffer-overflow on INSTALL PLUGIN |
| 119734 | 2026-01-21 14:08 | 2026-01-21 14:22 | MySQL Workbench | Open | S3 | Any | Any | MySQL Workbench Error – CSV Import Fails with ProgressBar Exception | |
| 119733 | 2026-01-21 11:41 | 2026-01-21 16:42 | Shell General / Core Client | Open (1 day) | S2 | 9.6.0 | Any | Any | SyntaxWarning for DbMySQLSession.py:360 |
| 119732 | 2026-01-21 5:25 | 2026-01-21 10:03 | MySQL Server | Not a Bug (1 day) | S3 | 9.5.0 | Any | Any | Floating-point precision loss happen after changing SUM(x) to -SUM(-x) |
| 119729 | 2026-01-20 17:17 | 2026-01-21 9:27 | MySQL Server: Optimizer | Verified (1 day) | 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 (2 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 (2 days) | S3 | 8.0.44 | Any | Any | after changing asin function in group clause,column's value unexpectedly change |
| 119720 | 2026-01-19 17:37 | 2026-01-20 8:29 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (2 days) | S3 | 9.3.0-cluster | Ubuntu | Any | Inconsistant result while executing functionally equivalent queries |
| 119716 | 2026-01-19 1:36 | 2026-01-19 9:16 | MySQL Server: Optimizer | Verified (3 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 (3 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 (2 days) | S3 | 8.0.39, 8.0.44, 8.4.6 | Any | Any | MySQL has hard time using the right indexes |
| 119710 | 2026-01-17 8:16 | 2026-01-19 8:03 | MySQL Server: Optimizer | Not a Bug (3 days) | S3 | 8.0.x, 8.4.x | Any | Any | column value unexpectedly change ,after changing atan2 function |
| 119703 | 2026-01-16 7:26 | 2026-01-16 13:03 | MySQL Server | Not a Bug (6 days) | S3 | 8.0.x, 8.4.x | Any | Any | after changing log function,the col_3’s value unexpectedly change |
| 119702 | 2026-01-16 7:21 | 2026-01-16 9:53 | MySQL Server | Not a Bug (6 days) | S3 | 8.0.x, 8.4.x | Any | Any | after changing max to -min(-),the col_3’s floating-precission loss appear |
| 119701 | 2026-01-16 7:18 | 2026-01-16 9:45 | MySQL Server: Optimizer | Verified (6 days) | 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 (6 days) | S3 | 8.0.44 | Any | Any | column value unexpectedly change after adding distinct |
| 119699 | 2026-01-16 7:11 | 2026-01-16 9:27 | MySQL Server | Duplicate (6 days) | S3 | 8.0.x, 8.4.x | Any | Any | column name unexpectedly changes ,after adding DISTINCT |
| 119698 | 2026-01-16 7:08 | 2026-01-16 9:16 | MySQL Server: Optimizer | Verified (6 days) | 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 (6 days) | 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 (6 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 (6 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 (6 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 (6 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 (6 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 (7 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 (7 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 (7 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 (7 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 (7 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 (7 days) | S3 | 8.0.44 | Any | Any | after changing AVG(cte.col_2) to -AVG(-cte.col_2) ,rows become less |
| Showing 1-30 of 14944 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
