| Showing 1-30 of 55 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 95698 | 2019-06-07 22:40 | 2025-05-04 6:30 | MySQL Server: JSON | Verified (58 days) | S3 | 8.0, 8.0.16, 5.7.26 | Any | Any | JSON columns are returned with binary charset |
| 117927 | 2025-04-10 6:25 | 2025-04-10 7:35 | MySQL Server: JSON | Verified (82 days) | S2 | 8.0.41, 8.4 | Any | Any | duplicate key in table while using tmp table for group by a json data |
| 117674 | 2025-03-12 6:20 | 2025-03-17 9:46 | MySQL Server: JSON | Verified (106 days) | S2 | 8.0.37, 8.0.41, 8.4.4 | Any | Any | JSON value is not recognized by Mysql inside Stored Routines |
| 117663 | 2025-03-11 8:29 | 2025-03-11 8:57 | MySQL Server: JSON | Verified (112 days) | S3 | 9.2.0 | Any | Any | JSON_ARRAY func result error |
| 117454 | 2025-02-13 2:08 | 2025-02-13 5:48 | MySQL Server: JSON | Verified (138 days) | S2 | 8.4.1 9.1.0 , 8.0.41 | Windows (windows 11) | x86 (x86_64) | Unexpected results with JSON_VALID function in WHERE clause. |
| 117235 | 2025-01-18 7:00 | 2025-01-20 6:07 | MySQL Server: JSON | Verified (162 days) | S3 | 8.4.1,9.1.0, 8.0.40, 8.4.3 | Windows | x86 | Unexpected results when using JSON_ARRAY comparison as a predicate. |
| 117234 | 2025-01-18 6:35 | 2025-01-20 5:58 | MySQL Server: JSON | Verified (162 days) | S2 | 8.4.1,9.1.0, 8.0.40, 8.4.3 | Windows | x86 | Unexpected results when using JSON_ARRAY(NULL) in query predicates. |
| 116852 | 2024-12-03 3:33 | 2024-12-03 6:17 | MySQL Server: JSON | Verified (210 days) | S3 | 8.0.34, 8.0.40 | Any | Any | Difference between JSONPath "$" vs "$[*]" |
| 116703 | 2024-11-19 6:06 | 2024-11-19 6:28 | MySQL Server: JSON | Verified (224 days) | S3 | 8.0.33, 8.0.40, 8.4.3, 9.1.0 | Any | Any | `JSON_VALID` has inconsistent behavior for `NULL` |
| 116688 | 2024-11-18 3:23 | 2024-11-18 6:46 | MySQL Server: JSON | Verified (225 days) | S2 | 8.0.36, 8.0.40, 8.4.3, 9.1.0 | Any | Any | Unexpected Behavior in `CASE` Statement with JSON Null Values |
| 116606 | 2024-11-10 6:44 | 2024-11-11 7:16 | MySQL Server: JSON | Verified (232 days) | S2 | 9.0, 8.0.40, 8.4.3, 9.1.0 | Any | Any | Incorrect Grouping in JSON_OBJECTAGG Aggregation for Case-Sensitive Column |
| 116300 | 2024-10-04 13:44 | 2024-10-04 14:34 | MySQL Server: JSON | Verified (270 days) | S2 | 9.0 | Any | Any | TINYBLOB and BLOB with same value, stored as JSON, become different |
| 116160 | 2024-09-19 10:28 | 2024-09-20 8:58 | MySQL Server: JSON | Verified (284 days) | S3 | 8.0 | Any | Any | Precision loss of double value in JSON |
| 115856 | 2024-08-18 12:56 | 2024-08-19 7:26 | MySQL Server: JSON | Verified (316 days) | S3 | 8.0, 8.4, 9.0 | Any | Any | Composite multi-valued index fails to be used for sorting |
| 113049 | 2023-11-10 15:28 | 2024-01-17 16:27 | MySQL Server: JSON | Verified (531 days) | S2 | 8.0.35, 8.2.0 | Any | Any | MTR test json.array_index fails with a result difference |
| 113641 | 2024-01-15 5:42 | 2024-01-15 5:50 | MySQL Server: JSON | Verified (533 days) | S2 | 8.0.28 | Any | Any | Multi-valued index can lead to incorrect result with implicit conversion |
| 113557 | 2024-01-04 15:29 | 2024-01-04 15:40 | MySQL Server: JSON | Verified (544 days) | S2 | 8.0.35 | Any | Any | Wrong query result on composite multi-valued index + empty array value |
| 112346 | 2023-09-14 8:21 | 2023-10-11 7:24 | MySQL Server: JSON | Verified (629 days) | S5 | 8.0.34 | Any | Any | MEMBER_OF with multi-valued index on JSON not used in 99% of situations. |
| 112147 | 2023-08-23 2:58 | 2023-08-24 7:31 | MySQL Server: JSON | Verified (678 days) | S3 | 8.0.34 | Any | Any | Use/Ignore Mutil-value index for MEMBER OF function has differnet result |
| 112053 | 2023-08-12 19:55 | 2023-08-21 12:36 | MySQL Server: JSON | Verified (685 days) | S3 | 8.0 | Any | Any | COALESCE a null value with a JSON object returns hex string |
| 111838 | 2023-07-21 10:51 | 2023-07-21 11:31 | MySQL Server: JSON | Verified (711 days) | S3 | 8.10 | Any | Any | Evaluate JSON column default on table/column creation |
| 111072 | 2023-05-18 10:12 | 2024-04-10 10:04 | MySQL Server: JSON | Verified (774 days) | S3 | 8.0.33, 5.7.42, 8.0.36 | Any | Any | The subquery involves JSON, and the execution result is incorrect. |
| 110556 | 2023-03-30 2:46 | 2023-03-30 6:19 | MySQL Server: JSON | Verified (824 days) | S2 | 8.0.28, 8.0.32 | Linux | Any | When we use json to build an index, we will get wrong results |
| 110487 | 2023-03-24 6:09 | 2023-03-24 9:20 | MySQL Server: JSON | Verified (830 days) | S3 | 5.7,8.0.32 | Any | Any | json array field ignored in multi sort. |
| 109893 | 2023-02-02 9:15 | 2023-02-02 10:11 | MySQL Server: JSON | Verified (880 days) | S3 | 8.0.31, 8.0.32 | Any | Any | json_contains always return 1 if candidate array is empty array |
| 108630 | 2022-09-28 10:46 | 2022-09-28 11:33 | MySQL Server: JSON | Verified (1007 days) | S3 | 5.7 | Linux (centos 7.5) | x86 | json query bug |
| 108365 | 2022-09-01 19:15 | 2023-10-02 19:05 | MySQL Server: JSON | Verified (1033 days) | S3 | 8.0.30 | Any | Any | JSON_TABLE fails to parse when used in LATERAL join |
| 108231 | 2022-08-23 5:15 | 2022-08-23 7:53 | MySQL Server: JSON | Verified (1043 days) | S3 | 5.7.37, 5.7.39, 8.0.30 | Any | Any | JSON_ARRAY_APPEND adds backslashes when a JSON_OBJECT passed as variable |
| 107199 | 2022-05-03 15:33 | 2022-05-12 19:40 | MySQL Server: JSON | Verified (1146 days) | S3 | 8.0.27 | Any | Any | Inconsistent JSON path ** behaviour between versions |
| 107225 | 2022-05-05 17:13 | 2023-11-29 17:30 | MySQL Server: JSON | Verified (1147 days) | S3 | 8.0 | Any | Any | IFNULL Stringifies JSON Object |
| Showing 1-30 of 55 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
