Wrong behavior when primary key is Unsigned int. #5112
Closed
Description
Please answer these questions before submitting your issue. Thanks!
- What did you do?
If possible, provide a recipe for reproducing the error.
create table t1 (a bigint unsigned not null, primary key(a));
insert into t1 values (18446744073709551615);
insert into t1 values (1);
select * from t1 order by a;
- What did you expect to see?
Two row, first is 1, second is 18446744073709551615.
- What did you see instead?
Two row, but first is 18446744073709551615, second is 1.
- What version of TiDB are you using (
tidb-server -V
)?
Activity