Repository navigation
Unexpected result when using JSON_VALID #56293
Copy link
Copy link
Closed
Labels
affects-6.5This bug affects the 6.5.x(LTS) versions.This bug affects the 6.5.x(LTS) versions.affects-7.1This bug affects the 7.1.x(LTS) versions.This bug affects the 7.1.x(LTS) versions.affects-7.5This bug affects the 7.5.x(LTS) versions.This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.This bug affects the 8.1.x(LTS) versions.affects-8.5This bug affects the 8.5.x(LTS) versions.This bug affects the 8.5.x(LTS) versions.fuzz/sqlancerimpact/wrong-resultseverity/moderatesig/sql-infraSIG: SQL InfraSIG: SQL Infratype/bugThe issue is confirmed as a bug.The issue is confirmed as a bug.
Description
Activity
- addedtype/bugThe issue is confirmed as a bug.The issue is confirmed as a bug.
on Sep 25, 2024 /label fuzz/sqlancer
- addedsig/sql-infraSIG: SQL InfraSIG: SQL Infra
on Sep 27, 2024 - addedmay-affects-5.4This bug maybe affects 5.4.x versions.This bug maybe affects 5.4.x versions.
on Sep 27, 2024 There is another case that the result is not compatible with MySQL:
SELECT * FROM t0 WHERE (JSON_VALID(t0.c1)=0);
TiDB (with TiKV) gives nothing, but TiDB (unistore) and MySQL gives one row. Maybe the implementation has some bugs in TiKV side.
Reacted by suyuz- addedaffects-8.5This bug affects the 8.5.x(LTS) versions.This bug affects the 8.5.x(LTS) versions.
on Nov 1, 2024 3 remaining items
- addedaffects-6.5This bug affects the 6.5.x(LTS) versions.This bug affects the 6.5.x(LTS) versions.affects-7.1This bug affects the 7.1.x(LTS) versions.This bug affects the 7.1.x(LTS) versions.affects-7.5This bug affects the 7.5.x(LTS) versions.This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.This bug affects the 8.1.x(LTS) versions.and removedmay-affects-5.4This bug maybe affects 5.4.x versions.This bug maybe affects 5.4.x versions.
on Nov 19, 2024 - added a commit that references this issue
on Nov 19, 2024 - added a commit that references this issue
on Nov 20, 2024
Metadata
Metadata
Assignees
Labels
affects-6.5This bug affects the 6.5.x(LTS) versions.This bug affects the 6.5.x(LTS) versions.affects-7.1This bug affects the 7.1.x(LTS) versions.This bug affects the 7.1.x(LTS) versions.affects-7.5This bug affects the 7.5.x(LTS) versions.This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.This bug affects the 8.1.x(LTS) versions.affects-8.5This bug affects the 8.5.x(LTS) versions.This bug affects the 8.5.x(LTS) versions.fuzz/sqlancerimpact/wrong-resultseverity/moderatesig/sql-infraSIG: SQL InfraSIG: SQL Infratype/bugThe issue is confirmed as a bug.The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
This could be reproduced on MySQL also, but still, I suspect it is unexpected.
2. What did you expect to see? (Required)
The second query returns a
NULLvalue or the third query returns the row in the table after join.3. What did you see instead (Required)
empty set
4. What is your TiDB version? (Required)