bug: Create table Primary key set AUTO_INCREMENT missing data in a certain case.

[nangong007]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Please confirm if bug report does NOT exists already ?

• I confirm there is no existing issue for this

Describe the problem

when set global tianmu_insert_delayed =ON，innodb_autoinc_lock_mode=1 ; and update primary key manually to a new value. Then will missing a row.

For example:
CREATE TABLE:
CREATE TABLE employees (
emp_no INT AUTO_INCREMENT PRIMARY KEY,
first_name VARCHAR(50),
last_name VARCHAR(50)
);
INSERT INTO employees(first_name,last_name)
VALUES('John','Doe'),
('Mary','Jane');

UPDATE employees
SET
first_name = 'Joe',
emp_no = 5
WHERE
emp_no = 2;

INSERT INTO employees(first_name,last_name)
VALUES('Wang2','Lee');
INSERT INTO employees(first_name,last_name)
VALUES('Wang3','Lee');
INSERT INTO employees(first_name,last_name)
VALUES('Wang4','Lee');
INSERT INTO employees(first_name,last_name)
VALUES('Wang5','Lee');
INSERT INTO employees(first_name,last_name)
VALUES('Wang6','Lee');

Result:
The row where first_name='Wang5' is missing

expecting:

The row where first_name='Wang5' should exist in table.

Expected behavior

No row missing

How To Reproduce

No response

Environment

No response

Are you interested in submitting a PR to solve the problem?

• Yes, I will!

[isredstar]

ACK

[isredstar]

void ha_tianmu::update_create_info([[maybe_unused]] HA_CREATE_INFO *create_info) {} is not implemented

[RingsC]

fix by #1315