executor,sessionctx: handle last_insert_id(0) like MySQL

[dveeden]

What problem does this PR solve?

Issue Number: close #58201

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.

Handling of `last_insert_id(0)` was changed to be compatible with MySQL

[tiprow]

Hi @dveeden. 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.

[dveeden]

/ok-to-test

[dveeden]

/check-issue-triage-complete

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.4754%. Comparing base (30069c5) to head (7cbe43c).
Report is 201 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58204        +/-   ##
================================================
+ Coverage   73.1633%   75.4754%   +2.3120%     
================================================
  Files          1674       1686        +12     
  Lines        461261     489468     +28207     
================================================
+ Hits         337474     369428     +31954     
+ Misses       103041      99424      -3617     
+ Partials      20746      20616       -130     

Flag	Coverage Δ
integration	45.1612% <100.0000%> (?)
unit	74.2333% <100.0000%> (+1.9436%)	⬆️

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

Components	Coverage Δ
dumpling	53.0100% <ø> (+0.3190%)	⬆️
parser	∅ <ø> (∅)
br	45.9370% <ø> (-0.0704%)	⬇️

[mjonss]

Please create a test as well? maybe in tests/integration?
Otherwise LGTM :)

[jackysp]

LGTM

[dveeden]

/cc @yudongusa @benmeadowcroft

[ti-chi-bot]

@dveeden: GitHub didn't allow me to request PR reviews from the following users: yudongusa, BenMeadowcroft.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @yudongusa @benmeadowcroft

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]

[LGTM Timeline notifier]

Timeline:

• 2024-12-15 08:10:11.18931105 +0000 UTC m=+771601.278113578: ☑️ agreed by jackysp.
• 2024-12-17 22:11:37.331379726 +0000 UTC m=+994887.420182265: ☑️ agreed by mjonss.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jackysp, lcwangchao, mjonss, yudongusa

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 [jackysp,lcwangchao,mjonss]
• pkg/sessionctx/variable/OWNERS [yudongusa]

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

[dveeden]

/retest

[tiprow]

@dveeden: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	7cbe43c	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[ti-chi-bot]

@dveeden: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/check_dev_2	7cbe43c	link	unknown	/test check-dev2

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.