Skip to content

Wrong behavior when primary key is Unsigned int. #5112

Closed
@winoros

Description

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 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;
  1. What did you expect to see?

Two row, first is 1, second is 18446744073709551615.

  1. What did you see instead?

Two row, but first is 18446744073709551615, second is 1.

  1. What version of TiDB are you using (tidb-server -V)?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

type/bugThe issue is confirmed as a bug.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions