bigint unsigned primary key duplicate error info is not correct

[cyliu0]

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.

Check the below symptoms.

2. What did you expect to see?
   On MySQL:

mysql> create table t(a bigint unsigned primary key);
Query OK, 0 rows affected (0.05 sec)

mysql> insert into t values(18446744073709551615);
Query OK, 1 row affected (0.01 sec)

mysql> insert into t values(18446744073709551615);
ERROR 1062 (23000): Duplicate entry '18446744073709551615' for key 'PRIMARY'

3. What did you see instead?
   On TiDB:

mysql> create table t(a bigint unsigned primary key);
Query OK, 0 rows affected (0.01 sec)

mysql> insert into t values(18446744073709551615);
Query OK, 1 row affected (0.01 sec)

mysql> insert into t values(18446744073709551615);
ERROR 1062 (23000): Duplicate entry '-1' for key 'PRIMARY'
mysql> select * from t;
+----------------------+
| a                    |
+----------------------+
| 18446744073709551615 |
+----------------------+
1 row in set (0.00 sec)

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

mysql> select tidb_version()\G
*************************** 1. row ***************************
tidb_version(): Release Version: v4.0.0-alpha-367-gde2df75a3-dirty
Git Commit Hash: de2df75a3e3cbebfa03e0d1ab33d6b70e6228eee
Git Branch: master
UTC Build Time: 2019-09-26 09:29:39
GoVersion: go version go1.12.9 darwin/amd64
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
1 row in set (0.00 sec)

[cyliu0]

Found this bug during review #10056 which has been fixed by #10113. Hope this might help.

[zz-jason]

Found this bug during review #10056 which has been fixed by #10113. Hope this might help.

So can we close issue?

[cyliu0]

Found this bug during review #10056 which has been fixed by #10113. Hope this might help.

So can we close issue?

Sry if I haven't cleared this out. I mean #10113 fixed #10056. But it doesn't fix this bug. They may related to this one.

[ghost]

Confirming issue still exists against master (it's minor):

drop table if exists t;
create table t(a bigint unsigned primary key);
insert into t values(18446744073709551615);
insert into t values(18446744073709551615);

..


mysql> insert into t values(18446744073709551615);
ERROR 1062 (23000): Duplicate entry '-1' for key 'PRIMARY'
mysql> 
mysql> SELECT tidb_version()\G
*************************** 1. row ***************************
tidb_version(): Release Version: v4.0.0-beta.2-821-gfe07417e6
Edition: Community
Git Commit Hash: fe07417e6b2f28eb334117d44640d0760d7e9866
Git Branch: master
UTC Build Time: 2020-07-22 12:51:37
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)

[ti-srebot]

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

[v3.0.0:v3.0.20], [v4.0.0:v4.0.10], [v5.0.0-rc]

6. Fixed versions

master

[ti-srebot]

The values in ( FixedVersions ) fields are incorrect.

[ti-srebot]

The values in ( FixedVersions ) fields are incorrect.

[ti-srebot]

The values in ( FixedVersions ) fields are incorrect.