Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Temp Table: Run auto_increment case in pessimistic mode multi times gets different result. #10903

Open
1 task done
Tracked by #7889
Ariznawlll opened this issue Jul 28, 2023 · 5 comments
Open
1 task done
Tracked by #7889
Assignees
Labels
attention/refactor-related kind/bug Something isn't working severity/s1 High impact: Logical errors or data errors that must occur
Milestone

Comments

@Ariznawlll
Copy link
Contributor

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Environment

- Version or commit-id (e.g. v0.1.0 or 8b23a93):1e2b2428e5743464f50abda83d5a06fdf54e36ae
- Hardware parameters:
- OS type:
- Others:

Actual Behavior

Run auto_increment case multi times occurs different result, as follows:
image

Expected Behavior

image

Steps to Reproduce

Drop table if exists auto_increment04;
Create temporary table auto_increment04(col1 int primary key auto_increment) auto_increment = 10;
insert into auto_increment04 values();
Select * from auto_increment04;
Insert into auto_increment04 values();
select last_insert_id();
Insert into auto_increment04 values(100);
Insert into auto_increment04 values(200);
Insert into auto_increment04 values(10);
Insert into auto_increment04 values(11);
Select * from auto_increment04;
Drop table auto_increment04;

Additional information

No response

@Ariznawlll Ariznawlll added kind/bug Something isn't working needs-triage severity/s0 Extreme impact: Cause the application to break down and seriously affect the use labels Jul 28, 2023
@Ariznawlll Ariznawlll added this to the 1.0.0 milestone Jul 28, 2023
@Ariznawlll Ariznawlll changed the title [Bug]: Run auto_increment case in pessimistic mode multi times occurs different result. [Bug]: Run auto_increment case in pessimistic mode multi times gets different result. Jul 28, 2023
@ouyuanning
Copy link
Contributor

not working on it

@ouyuanning
Copy link
Contributor

当前临时表的实现需要重构,以满足悲观事务的需求。
建议统一放在一个临时表重构的issue下。

@ouyuanning ouyuanning assigned Ariznawlll and unassigned ouyuanning Jul 31, 2023
@Ariznawlll Ariznawlll removed the severity/s0 Extreme impact: Cause the application to break down and seriously affect the use label Jul 31, 2023
@Ariznawlll
Copy link
Contributor Author

wating for temporary table refactor.

@matrix-meow
Copy link
Contributor

Hello @Ariznawlll. The bug issue in the BVT test code has not been removed,issues automatically open.

@matrix-meow matrix-meow reopened this Aug 23, 2023
@Ariznawlll Ariznawlll modified the milestones: 1.0.0, 1.1.0 Aug 24, 2023
@aressu1985 aressu1985 modified the milestones: 1.1.0, 1.2.0 Dec 26, 2023
@sukki37 sukki37 assigned ouyuanning and unassigned Ariznawlll Jan 25, 2024
@ouyuanning ouyuanning assigned reusee and unassigned ouyuanning Jan 25, 2024
@ouyuanning ouyuanning added the severity/s1 High impact: Logical errors or data errors that must occur label Jan 25, 2024
@aressu1985 aressu1985 modified the milestones: 1.2.0, 1.3.0-Backlog Apr 28, 2024
@sukki37 sukki37 modified the milestones: 1.3.0-Backlog, Backlog Jul 16, 2024
@sukki37 sukki37 added kind/refactor Code refactor attention/refactor-related and removed kind/refactor Code refactor labels Jul 16, 2024
@fengttt fengttt modified the milestones: Backlog, 2.0.1 Oct 29, 2024
@fengttt fengttt changed the title [Bug]: Run auto_increment case in pessimistic mode multi times gets different result. [Bug]: Temp Table: Run auto_increment case in pessimistic mode multi times gets different result. Oct 29, 2024
@fengttt fengttt modified the milestones: 2.0.1, Backlog Oct 29, 2024
@fengttt
Copy link
Contributor

fengttt commented Oct 29, 2024

This issue is also temp table related. Changed title. Keep all temp table issues in backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attention/refactor-related kind/bug Something isn't working severity/s1 High impact: Logical errors or data errors that must occur
Projects
None yet
Development

No branches or pull requests

8 participants