Skip to content

Conversation

yihong0618
Copy link
Contributor

@yihong0618 yihong0618 commented Jul 23, 2025

What problem does this PR solve?

This patch close 62564 by fixing the case when prepare NULL value when case when
prepare, and do not break the json value ref #54145

Issue Number: close #62564

Problem Summary:

What changed and how does it work?

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.

None

Copy link

ti-chi-bot bot commented Jul 23, 2025

Hi @yihong0618. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ti-chi-bot ti-chi-bot bot added needs-ok-to-test Indicates a PR created by contributors and need ORG member send '/ok-to-test' to start testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 23, 2025
Copy link

tiprow bot commented Jul 23, 2025

Hi @yihong0618. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@hawkingrei
Copy link
Member

/ok-to-test

@ti-chi-bot ti-chi-bot bot added ok-to-test Indicates a PR is ready to be tested. and removed needs-ok-to-test Indicates a PR created by contributors and need ORG member send '/ok-to-test' to start testing. labels Jul 23, 2025
Signed-off-by: yihong0618 <[email protected]>
Copy link

codecov bot commented Jul 23, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.3763%. Comparing base (e823930) to head (94ab0ae).
⚠️ Report is 56 commits behind head on master.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #62568        +/-   ##
================================================
+ Coverage   72.8667%   73.3763%   +0.5095%     
================================================
  Files          1762       1769         +7     
  Lines        486020     496757     +10737     
================================================
+ Hits         354147     364502     +10355     
- Misses       110216     110327       +111     
- Partials      21657      21928       +271     
Flag Coverage Δ
integration 42.3217% <100.0000%> (?)
unit 72.2008% <100.0000%> (+0.0853%) ⬆️

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

Components Coverage Δ
dumpling 52.8700% <ø> (+0.0896%) ⬆️
parser ∅ <ø> (∅)
br 46.0212% <ø> (-0.3169%) ⬇️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@lance6716 lance6716 changed the title ddl: fix CASE WHEN wrong result when prepare value is NULL types: fix CASE WHEN wrong result when prepare value is NULL Jul 27, 2025
@lance6716 lance6716 requested a review from Lloyd-Pottiger July 27, 2025 13:27
Signed-off-by: yihong0618 <[email protected]>
@hawkingrei
Copy link
Member

/check-issue-triage-complete

Copy link
Member

@YangKeao YangKeao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM

Copy link
Member

@hawkingrei hawkingrei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I test this PR with fuzz tools and don't find the new bug.

@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jul 28, 2025
@hawkingrei
Copy link
Member

/hold

waiting for the other's approve

@ti-chi-bot ti-chi-bot bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 28, 2025
Copy link
Member

@YangKeao YangKeao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

ti-chi-bot bot commented Jul 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, 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 [YangKeao,hawkingrei]

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

@YangKeao
Copy link
Member

/unhold

@ti-chi-bot ti-chi-bot bot added lgtm and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jul 28, 2025
Copy link

ti-chi-bot bot commented Jul 28, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-07-28 08:58:50.778682263 +0000 UTC m=+257539.245245050: ☑️ agreed by hawkingrei.
  • 2025-07-28 10:43:19.643315325 +0000 UTC m=+263808.109878101: ☑️ agreed by YangKeao.

@hawkingrei
Copy link
Member

/unhold

@ti-chi-bot ti-chi-bot bot merged commit 312226f into pingcap:master Jul 28, 2025
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm ok-to-test Indicates a PR is ready to be tested. release-note-none Denotes a PR that doesn't merit a release note. sig/planner SIG: Planner size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CASE WHEN returns different result in prepared statement and normal query
4 participants