executor: fix mysql_insert_id() for "INSERT .. ON DUPLICATE KEY" statement (#56514)

[ti-chi-bot]

This is an automated cherry-pick of #56514

What problem does this PR solve?

Issue Number: close #55965

Problem Summary:

What changed and how does it work?

Handle the value correctly for mysql_insert_id() when duplicate update happen in the "INSERT .. ON DUPLICATED UPDATE" statement.

In the code internally, we use InsertID when the value auto increment column is specified explicitly.
And use LastInsertID when the value of auto increment column is auto generated.

	// PrevLastInsertID is the last insert ID of previous statement.
	PrevLastInsertID uint64
	// LastInsertID is the auto-generated ID in the current statement.
	LastInsertID uint64
	// InsertID is the given insert ID of an auto_increment column.
	InsertID uint64

The different between mysql_insert_id() and LAST_INSERT_ID() is that the former get its value either from auto generated or explicitly specified, while the later just update the value in the auto generated cases.

Check List

Tests

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

See the steps descriped in the issue

• 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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lcwangchao, tiancaiamao

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 [lcwangchao,tiancaiamao]

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-12-10 10:25:37.637378139 +0000 UTC m=+347727.726180681: ☑️ agreed by lcwangchao.
• 2024-12-10 14:38:42.786643917 +0000 UTC m=+362912.875446448: ☑️ agreed by tiancaiamao.

[tiancaiamao]

/test unit-test

[tiprow]

@tiancaiamao: No presubmit jobs available for pingcap/tidb@release-7.5

In response to this:

/test unit-test

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-7.5@972d702). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #58120   +/-   ##
================================================
  Coverage               ?   72.1512%           
================================================
  Files                  ?       1415           
  Lines                  ?     412999           
  Branches               ?          0           
================================================
  Hits                   ?     297984           
  Misses                 ?      95034           
  Partials               ?      19981           

Flag	Coverage Δ
unit	72.1512% <100.0000%> (?)

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

Components	Coverage Δ
dumpling	52.9400% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.5282% <0.0000%> (?)