We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please answer these questions before submitting your issue. Thanks!
create table test1(c1 varchar(100) not null default 'xyza', c2 int, primary key(c1(3)) clustered); replace into test1(c2) values(1); replace into test1(c2) values(1);
two replace successed
last replace failed with
replace into test1(c2) values(1); ERROR 1062 (23000): Duplicate entry 'xyz' for key 'PRIMARY'
Release Version: v4.0.0-beta.2-2243-g7daf7436d Edition: Community Git Commit Hash: 7daf7436da5de4e5fea3895e892d10d3790e9102 Git Branch: master UTC Build Time: 2021-03-03 06:18:37 GoVersion: go1.15 Race Enabled: false TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306 Check Table Before Drop: false
The text was updated successfully, but these errors were encountered:
insert on duplicate without default value also have same problem
create table test3(c1 varchar(100), c2 int, primary key(c1(1)) clustered); insert into test3 values('ab', 1) on duplicate key update c2 = 100; insert into test3 values('ab', 1) on duplicate key update c2 = 100; ERROR 1062 (23000): Duplicate entry 'a' for key 'PRIMARY'
Sorry, something went wrong.
Note: Make Sure that 'component', and 'severity' labels are added Example for how to fill out the template: #20100
master
lysu
Successfully merging a pull request may close this issue.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
two replace successed
3. What did you see instead (Required)
last replace failed with
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: