| Showing all 16 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 118224 | 2025-05-19 2:46 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (225 days) | S3 | 8.0.41 | Any | Any | When a constant value is replaced by the LEST function, the sql returns different value; |
| 118268 | 2025-05-26 7:47 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (232 days) | S3 | 8.0.41 | Any | Any | The returned results of two queries with the same semantics are inconsistent. |
| 118277 | 2025-05-27 8:02 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (232 days) | S3 | 8.0.41 | Any | Any | When a constant value is replaced by the IFNULL(NULL, CONST_VALUE) function, the sql returns different value; |
| 118278 | 2025-05-27 8:29 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (232 days) | S3 | 8.0.41 | Any | Any | two query SQL statements filling with opposite semantics in the where clause, result same result |
| 118298 | 2025-05-29 2:46 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (230 days) | S3 | 8.0.41 | Any | Any | "(t1.c4)<-(-1.7976931348623157E308)" and "(t1.c4)<(1.7976931348623157E308)" in where clause return different results |
| 118310 | 2025-05-30 3:36 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (229 days) | S3 | 8.0.41 | Any | Any | a query with a impossile having clause, return wrong results |
| 118336 | 2025-06-03 8:24 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (225 days) | S3 | 8.0.41 | Any | Any | after adding a having clause equivalent to "having 1", the returned result set is wrong |
| 118348 | 2025-06-04 1:52 | 2025-06-04 11:35 | MySQL Server: DML | Duplicate (224 days) | S3 | 8.0.41 | Any | Any | using force index(i0) and ignore index(i0) for the same query, the result set changed |
| 118353 | 2025-06-04 6:29 | 2025-06-04 11:58 | MySQL Server: DDL | Duplicate (224 days) | S4 | 8.0.41 | Any | Any | creating a view with select default(col) clause, return an err: denied to user XX for column 'DEFAULT(col)'. |
| 118369 | 2025-06-05 11:21 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (223 days) | S3 | 8.0.41 | Any | Any | "having column" and "having MIN(column)" return different result.something wrong during Aggregate using temporary table |
| 118375 | 2025-06-06 3:41 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (222 days) | S3 | 8.0.41 | Any | Any | while (NOT ((t0.c1) >= (t1.c2))) returns 1 actually, the query return an empty result set. |
| 118393 | 2025-06-09 1:36 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (219 days) | S3 | 8.0.41 | Any | Any | while the having subquery return NULL actually, the query using this having query returns a wrong result. |
| 118394 | 2025-06-09 2:04 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (219 days) | S3 | 8.0.41 | Any | Any | while (NOT XX NOT IN ()) return 0, the query with where (NOT XX NOT IN ()) returns a wrong result. |
| 118464 | 2025-06-17 7:24 | 2025-09-21 20:45 | MySQL Server: DML | Analyzing (211 days) | S3 | 8.0.41 | Any | Any | Inserting into a float value exceeding the precision, using IF function and using the column return different result. |
| 118571 | 2025-07-02 7:27 | 2025-08-06 12:50 | MySQL Server: DML | Duplicate (161 days) | S3 | 8.0.41 | Any | Any | using index lookup, the query return a wrong result; |
| 118627 | 2025-07-10 7:26 | 2025-07-23 13:04 | MySQL Server: DML | Not a Bug (175 days) | S3 | 8.0.41 | Any | Any | while exexuting prepare statement including 'order by ?', the sort of result set is not right |
| Showing all 16 (Edit, Save, CSV, Feed) |
