| Showing 1-30 of 31 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 106493 | 2022-02-17 14:38 | 2022-04-11 12:28 | MySQL Server: Replication | Verified (1476 days) | S3 | 8.0.28, 5.7.37 | Any | Any | Replication crash when updating a table with a stored generated field in the pri |
| 106560 | 2022-02-24 14:51 | 2023-10-19 10:51 | MySQL Server: DDL | Duplicate (1468 days) | S3 | 8.0.28 | Any | Any | slow DDL in mysql 8.0 as compare to 5.7 taking more time for checking permission |
| 112289 | 2023-09-07 11:32 | 2024-12-06 12:03 | MySQL Server: DML | Duplicate (909 days) | S2 | 8.0.34 | Any | Any | No error seen when unknown column is used in subquery for Update Statement |
| 112935 | 2023-11-02 10:05 | 2023-11-02 13:40 | MySQL Server | Duplicate (854 days) | S2 | 8.0.35 | Any | Any | Different Behaviour Seen Between MyISAM and MEMORY Engine |
| 115605 | 2024-07-16 11:27 | 2024-07-17 9:52 | MySQL Server: Replication | Verified (596 days) | S2 | 8.0.38 | Any | Any | START REPLICA doesn't start the SQL_THREAD |
| 116118 | 2024-09-16 8:51 | 2024-09-16 13:19 | MySQL Server: InnoDB storage engine | Verified (535 days) | S3 | 8.0.39 | Any | Any | Need to bound optimise-like statement in order to reclaim the disk space back |
| 116398 | 2024-10-17 14:34 | 2024-10-25 9:40 | MySQL Server: Optimizer | Verified (496 days) | S2 | 8.0 | Any | Any | Incorrect result with LEFT JOIN and small join_buffer_size |
| 116803 | 2024-11-27 11:29 | 2025-03-22 0:37 | MySQL Server: Optimizer | Verified (451 days) | S5 | 8.0.40 | Any | Any | MySQL 8.0.33 is slower than MySQL 8.0.28 with queries using JOINS |
| 117057 | 2024-12-27 12:35 | 2024-12-27 13:16 | MySQL Server: DML | Verified (433 days) | S3 | 8.4.3, 8.0.40 | Any | Any | Inconsistent Results Between Materialized Table and View with GREATEST |
| 117058 | 2024-12-27 13:01 | 2024-12-27 13:16 | MySQL Server: DML | Verified (433 days) | S3 | 8.4.3, 8.0.40 | Any | Any | Inconsistent Results When Using COALESCE |
| 117059 | 2024-12-27 13:14 | 2024-12-27 13:17 | MySQL Server: DML | Verified (433 days) | S3 | 8.4.3, 8.0.40 | Any | Any | Inconsistent Query Results Between Materialized Table and View with Division |
| 117060 | 2024-12-27 13:28 | 2024-12-27 13:39 | MySQL Server: DML | Verified (433 days) | S3 | 8.4.3, 8.0.40 | Any | Any | changing a constant TRUE to a condition involving TO_DAYS leads to a different result set |
| 118862 | 2025-08-20 14:05 | 2025-08-21 6:28 | MySQL Server: Optimizer | Verified (196 days) | S3 | 8.0.x, 8.4.x, 8.0.43 | Any | Any | MySQL Returns Incorrect Results for Complex Query with Set Operations |
| 118863 | 2025-08-20 14:23 | 2025-08-21 6:30 | MySQL Server: Optimizer | Verified (196 days) | S2 | 8.4.x, 8.4.6 | Any | Any | Complex collection query incorrectly missing '0' |
| 119312 | 2025-11-05 17:30 | 2026-01-13 11:33 | MySQL Server: Replication | Open | S3 | 8.4.x | Any | Any | `start replica` command adds an invalid record to mysql.slave_master_info |
| 119693 | 2026-01-16 6:39 | 2026-01-16 8:28 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.0.44 | Any | Any | column value change after changing INNER to LEFT |
| 119694 | 2026-01-16 6:56 | 2026-01-16 8:39 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.0.44 | Any | Any | rows unexpectedly become less after changing INNER to LEFT |
| 119695 | 2026-01-16 6:59 | 2026-01-16 8:48 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.0.44 | Any | Any | The appearance of rows that should not exist caused by on clause |
| 119696 | 2026-01-16 7:03 | 2026-01-16 8:58 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.0.44 | Any | Any | float value Precision loss caused by removing distinct |
| 119697 | 2026-01-16 7:06 | 2026-01-22 13:08 | MySQL Server: Optimizer | Duplicate (42 days) | S3 | 8.0.44 | Any | Any | Bit value changed after adding DISTINCT in query |
| 119698 | 2026-01-16 7:08 | 2026-01-16 9:16 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.0. | Any | Any | rows become less unexpectedly caused by on clause |
| 119699 | 2026-01-16 7:11 | 2026-01-16 9:27 | MySQL Server | Duplicate (48 days) | S3 | 8.0.x, 8.4.x | Any | Any | column name unexpectedly changes ,after adding DISTINCT |
| 119700 | 2026-01-16 7:14 | 2026-01-22 13:16 | MySQL Server: Optimizer | Duplicate (42 days) | S3 | 8.0.44 | Any | Any | column value unexpectedly change after adding distinct |
| 119701 | 2026-01-16 7:18 | 2026-01-16 9:45 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.0.44 | Any | Any | after changing FLOOR function,col_1’s value unexpectedly change |
| 119702 | 2026-01-16 7:21 | 2026-01-16 9:53 | MySQL Server | Not a Bug (48 days) | S3 | 8.0.x, 8.4.x | Any | Any | after changing max to -min(-),the col_3’s floating-precission loss appear |
| 119703 | 2026-01-16 7:26 | 2026-01-16 13:03 | MySQL Server | Not a Bug (48 days) | S3 | 8.0.x, 8.4.x | Any | Any | after changing log function,the col_3’s value unexpectedly change |
| 119710 | 2026-01-17 8:16 | 2026-01-19 8:03 | MySQL Server: Optimizer | Not a Bug (45 days) | S3 | 8.0.x, 8.4.x | Any | Any | column value unexpectedly change ,after changing atan2 function |
| 119713 | 2026-01-18 11:19 | 2026-01-20 9:37 | MySQL Server: Optimizer | Verified (44 days) | S3 | 8.0.39, 8.0.44, 8.4.6 | Any | Any | MySQL has hard time using the right indexes |
| 119714 | 2026-01-18 12:26 | 2026-01-19 9:01 | MySQL Server: Optimizer | Verified (45 days) | S3 | 8.0.44 | Any | Any | after changing ASIN(hpg31.c1) in group clause,the col_1’s value unexpectedly change. |
| 119778 | 2026-01-26 12:56 | 2026-01-29 9:27 | MySQL Server: Optimizer | Duplicate (35 days) | S3 | 8.0.x, 8.4.x | Any | Any | after changing SUM(distinct x) to - SUM(distinct -x),the value unexpectedly change |
| Showing 1-30 of 31 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
