MySQL primary/foreign key size?

The size is neither bits nor bytes. It's just the display width, that is used when the field has ZEROFILL specified and INT(M) UNSIGNED ZEROFILL A normal-size integer. The signed range is -2147483648 to 2147483647.

The unsigned range is 0 to 4294967295 See this explanation.

The size is neither bits nor bytes. It's just the display width, that is used when the field has ZEROFILL specified. And INT(M) UNSIGNED ZEROFILL A normal-size integer.

The signed range is -2147483648 to 2147483647. The unsigned range is 0 to 4294967295. See this explanation.

I don't see any good reason to use a number larger than 32-bit integer for indexing data in normal business-sized databases. Most of them have maybe millions of records (or that order of magnitude).

Neither does MySQL. They use 32-bit integers for the INT data type. The number in () has no bearing on the number of bits.

– Eric J. May 15 '10 at 18:04.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.