expression: fix the collation of functions with json arguments (#53126)

[ti-chi-bot]

This is an automated cherry-pick of #53126

What problem does this PR solve?

Issue Number: close #52833

Problem Summary:

MySQL will use binary collation when the max_length of some arguments' types are too long. It'll mostly happen on JSON types.

What changed and how does it work?

As TiDB doesn't have a max_length attribute for each type and "datum", I specially handled the situation for JSON. Some function will return binary collation when some of the arguments are JSON type.

In MySQL, the state of BINARY flag, BLOB type and binary collation is really a chaos. For this example, you'll find that sometimes the collation(...) returns utf8mb4_bin while the returned type info (shown through --column-type-info) tells you the collation is utf8mb4_0900_ai_ci. I'm not sure whether it's a bug for MySQL or not...

So, I want to fix the behavior with minimum modification: only change the collation to binary collation and don't touch the charset.

Check List

Tests

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

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Fix the issue that the collation of the result of some functions are not compatible with MySQL when the arguments contain JSON.

[codecov]

Codecov Report

Attention: Patch coverage is 92.30769% with 3 lines in your changes are missing coverage. Please review.

❗ No coverage uploaded for pull request base (release-8.1@870c1fd). Click here to learn what that means.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.1     #53199   +/-   ##
================================================
  Coverage               ?   71.2467%           
================================================
  Files                  ?       1465           
  Lines                  ?     421799           
  Branches               ?          0           
================================================
  Hits                   ?     300518           
  Misses                 ?     100823           
  Partials               ?      20458           

Flag	Coverage Δ
unit	71.2467% <92.3076%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	40.9907% <0.0000%> (?)

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: XuHuaiyu, YangKeao

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [XuHuaiyu,YangKeao]
• pkg/expression/OWNERS [XuHuaiyu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-05-13 06:04:59.624613157 +0000 UTC m=+1460453.381748732: ☑️ agreed by XuHuaiyu.
• 2024-05-13 06:25:23.778547962 +0000 UTC m=+1461677.535683530: ☑️ agreed by YangKeao.

[YangKeao]

/retest

[YangKeao]

/retest