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

Wrong result when update ... set ... on same table #11911

Closed
Deardrops opened this issue Aug 28, 2019 · 6 comments · Fixed by #20493
Closed

Wrong result when update ... set ... on same table #11911

Deardrops opened this issue Aug 28, 2019 · 6 comments · Fixed by #20493
Assignees
Labels
challenge-program help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. severity/critical sig/execution SIG execution type/bug The issue is confirmed as a bug.
Milestone

Comments

@Deardrops
Copy link
Contributor

Deardrops commented Aug 28, 2019

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If possible, provide a recipe for reproducing the error.
create table t(x int, y int);
insert into t values();
update t t1, t t2 set t2.y=1, t1.x=2;
select * from t;
  1. What did you expect to see?

image

  1. What did you see instead?

image

  1. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?

image

SIG slack channel

#sig-exec

Score

  • 300

Mentor

@Deardrops Deardrops added the type/bug The issue is confirmed as a bug. label Aug 28, 2019
@ghost
Copy link

ghost commented Jul 15, 2020

Confirming this issue still exists in master:

DROP TABLE IF EXISTS t;
create table t(x int, y int);
insert into t values();
update t t1, t t2 set t2.y=1, t1.x=2;
select * from t;

..

mysql> select * from t;
+------+------+
| x    | y    |
+------+------+
|    2 | NULL |
+------+------+
1 row in set (0.00 sec)

mysql> select tidb_version()\G
*************************** 1. row ***************************
tidb_version(): Release Version: v4.0.0-beta.2-771-gca41972fb
Edition: Community
Git Commit Hash: ca41972fbac068c8a5de107d9075f09ac68842ac
Git Branch: master
UTC Build Time: 2020-07-14 02:41:21
GoVersion: go1.13
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
1 row in set (0.00 sec)

@qw4990 qw4990 added severity/critical sig/execution SIG execution help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Aug 26, 2020
@time-and-fate
Copy link
Member

/assign time-and-fate

@SunRunAway
Copy link
Contributor

cc @dyzsr

@jebter
Copy link

jebter commented Nov 4, 2020

/assign dyzsr

@scsldb scsldb modified the milestones: v4.0.11, v4.0.9 Nov 4, 2020
@dyzsr
Copy link
Contributor

dyzsr commented Nov 11, 2020

/assign

@ti-srebot
Copy link
Contributor

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
challenge-program help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. severity/critical sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants