json: implement json unary not with comparing to json(0)

[YangKeao]

Signed-off-by: YangKeao yangkeao@chunibyo.icu

What problem does this PR solve?

Issue Number: close #40683

Problem Summary:

The behavior of unary not for json value is different between TiDB and MySQL. TiDB converts the json to double and run unary not on it. MySQL compares the JSON with json integer 0.

What is changed and how it works?

I changed the behavior to be compatible with MySQL. The only concern is that I don't know whether returning a function in other function class is expected. I only noticed the funcName is different so I added a very ugly condition to overwrite the funcName, but I'm not sure whether it will have other problems (at least, I cannot overwrite the funcName for the caller...).

Or anyone can provide better idea?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Release note

Fix the issue that unary not with comparing to json(0) is not compatible with MySQL.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[xiongjiwei]

why not like the other type, add a new sig builtinUnaryNotJSONSig

[YangKeao]

Good. I also agree add a new sig builtinUnaryNotJSONSig is better 🤝

[YangKeao]

I'll add a new builtinUnaryNotJSONSig, but not using the eq directly.