Is it good idea to use uint instead of int as the primary key in data model class?

Question

We know that the primary keys are usually positive integers.

Is it good idea to use uint instead of int as the primary key in data model cl

Answer 1

In case somebody else stumbles on this question - don't use uint for your keys. I've just tried that with Entity Framework 6.1.12 and code kept failing with cryptic "Entity doesn't have key" exception.

Only after I've changed uint property back to int it started working as expected.

So, yeah, it sucks to have 2+ billion range unused, but that's how things are. And if you have even a slight doubt that you may end up with billion plus records, go with long. Ironically, then you'll have 9,223,372,036,854,775,808 numbers unused ;).

Answer 2

uint is not CLS compliant, so it's generally recommended not to use it in public APIs.

Answer 3

The corresponding SQL data type is a signed number, so I'd stick with the int to avoid any surprises.

Answer 4

I think it's bad idea, cause of int type is more optimized for using in .NET Framework.