| Showing all 25 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 35724 | 2008-03-31 22:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6247 days) | S2 | MySQL 5.0.51a-community-nt, 5.1, 6.0 BK | Any | Any | Non-found left join data passed as a parameter to a function in WHERE |
| 44397 | 2009-04-22 2:46 | 2012-05-18 20:19 | MySQL Server: FULLTEXT search | Verified (6198 days) | S2 | 5.0.79, 5.1.33, 5.1.34, 6.0.9 | Any | Any | Negative relevancy value for boolean fulltext query using a left join |
| 50357 | 2010-01-15 9:15 | 2012-05-18 20:19 | MySQL Server: Backup | Patch queued (5885 days) | S3 | 6.0-backup | Any | Any | Innodb blob+text columns: empty strings become NULL after restore |
| 51521 | 2010-02-25 18:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5888 days) | S2 | 5.1.42, 5.1.45-bzr | Any | Any | MERGE Algorithm in LEFT JOIN retuns 0000-00-00 instead of NULL |
| 52752 | 2010-04-12 6:15 | 2018-06-24 20:45 | MySQL Workbench: SQL Editor | Verified (5843 days) | S3 | 5.2.17 OSS | Windows | Any | SQL Editor does not check whether a NOT NULL column has a default value of NULL |
| 62548 | 2011-09-27 10:22 | 2015-05-16 14:26 | MySQL Server: Memory storage engine | Verified (5310 days) | S2 | 5.1.49, 5.1.58 | Linux (Ubuntu) | Any | Different result from memory and myisam table |
| 68864 | 2013-04-04 8:17 | 2013-04-04 8:37 | MySQL Server: Data Types | Verified (4755 days) | S2 | 5.6.10 | Any | Any | INTERVAL treats null values of text columns as float/int |
| 76596 | 2015-04-05 15:54 | 2015-04-06 6:42 | MySQL Workbench: Modeling | Verified (4023 days) | S3 | 6.2.5.0 build 397 (64 bits) | Windows (7 64 bits) | Any | Loss of Default NULL value |
| 80019 | 2016-01-17 17:34 | 2016-01-18 7:59 | MySQL Workbench: Modeling | Verified (3736 days) | S2 | 6.3.6 Build 511 CE 64-bit | Windows (7 Professional) | Any | Default value NULL gets erased merely by clicking to a default value field |
| 81010 | 2016-04-08 10:34 | 2020-01-24 10:45 | MySQL Server: DDL | Verified (3652 days) | S3 | 5.7.11, 5.6.29, 8.0.17 | Windows | Any | ALTER TABLE DROP DEFAULT - default value of NULL not forced |
| 84088 | 2016-12-07 8:24 | 2016-12-12 12:37 | MySQL Server: DML | Verified (3407 days) | S3 | 5.6.29-log, 5.6.34, 5.5.53 | Linux (CentOS6.5) | Any | how operate null value in MySQL? |
| 100670 | 2020-08-28 6:51 | 2020-08-28 7:13 | MySQL Server: Optimizer | Verified (2052 days) | S3 | 8.0.21, 5.7.31, 5.6.48 | Any | Any | Undescribed behavior of INTERVAL function with NULL |
| 100822 | 2020-09-12 14:39 | 2023-02-20 1:47 | MySQL Server: DML | Verified (1813 days) | S3 | 8.0/5.7/5.6 | Red Hat (7.4) | Any | the result of group_concat(field1 order by field2) is unexpect. |
| 103233 | 2021-04-07 6:58 | 2021-04-07 7:35 | MySQL Server: Optimizer | Verified (1830 days) | S2 | 5.7.33 | CentOS | Any | wrong results when comparing to null |
| 106297 | 2022-01-26 22:39 | 2022-01-27 6:00 | MySQL Server: Optimizer | Verified (1535 days) | S2 | 8.0.27, 8.0.28 | Ubuntu (Ubuntu 20.04.3 LTS) | x86 (x86 (Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz)) | Incorrect outputs when combine unique index with NULL |
| 107438 | 2022-05-31 19:57 | 2023-05-02 16:49 | MySQL Server: Replication | Verified (1410 days) | S2 | 5.7.38 | CentOS (8) | Any | JSON STORED generated column values are inserted as NULL on replica |
| 109354 | 2022-12-13 5:43 | 2022-12-13 7:15 | MySQL Server: Optimizer | Verified (1215 days) | S3 | 8.0.21, 8.0.30, 8.0.31 | Any | Any | Numeric format change caused by DISTINCT, UNION and NULL |
| 110563 | 2023-03-30 8:21 | 2023-03-30 8:48 | MySQL Server: Optimizer | Verified (1108 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | NULL safe equality operator query with wrong result |
| 120102 | 2026-03-19 1:34 | 2026-03-19 8:22 | MySQL Server: JSON | Verified (23 days) | S3 | 8.0.45 | Any | Any | Incorrect DISTINCT behavior with JSON_ARRAYAGG when aggregating NULL-only groups |
| 120109 | 2026-03-19 9:01 | 2026-03-19 14:03 | MySQL Server: JSON | Verified (23 days) | S3 | 8.0.45 | Any | Any | Wrong result: DISTINCT eliminates JSON_ARRAY(NULL) result |
| 120110 | 2026-03-19 9:04 | 2026-03-19 14:07 | MySQL Server: JSON | Verified (23 days) | S3 | 8.0.45 | Any | Any | Wrong result: DISTINCT eliminates JSON_OBJECT result containing NULL value |
| 120111 | 2026-03-19 9:14 | 2026-03-19 14:10 | MySQL Server: JSON | Verified (23 days) | S3 | 8.0.45 | Any | Any | Unexpected row elimination when using DISTINCT on JSON_SET output |
| 120152 | 2026-03-25 8:50 | 2026-03-26 9:05 | MySQL Server: Optimizer | Verified (16 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | Unexpected behavior of LEFT JOIN + empty subquery with NULL comparison in WHERE clause |
| 120159 | 2026-03-26 11:41 | 2026-03-27 4:57 | MySQL Server: Optimizer | Verified (16 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | RIGHT JOIN + Complex Subqueries Returns Extra Rows |
| 120187 | 2026-03-31 11:46 | 2026-03-31 11:46 | MySQL Server | Open | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | Bug: COUNT(*) vs SUM(CASE WHEN ...) returns inconsistent results with NULL-sensitive joins |
| Showing all 25 (Edit, Save, CSV, Feed) |
