[pgo]

Are TINYINT(3), INT(3), SMALLINT(3) all the same?

My feeble mind is having trouble with the "length" thing. Am I correct in thinking that it means the number of digits - assuming UNSIGNED: (2) would be 0-99, (3) would be 0-999.

That right?

[dtrenz]

yes, 3 equals length of digits.
and yes, i believe they are all the same (some deprecated), much like text and blob or bool and boolean.

[2Dfruit]

i also think it has something to do with the amount of decimals it can handle...i think

[paulanthony]

bigint

Integer (whole number) data from -2^63 (-9,223,372,036,854,775,808) through 2^63-1 (9,223,372,036,854,775,807). Storage size is 8 bytes.

int

Integer (whole number) data from -2^31 (-2,147,483,648) through 2^31 - 1 (2,147,483,647). Storage size is 4 bytes. The SQL-92 synonym for int is integer.

smallint

Integer data from -2^15 (-32,768) through 2^15 - 1 (32,767). Storage size is 2 bytes.

tinyint

Integer data from 0 through 255. Storage size is 1 byte.

[pgo]

So, the only difference between INT(3) UNSIGNED, and SMALLINT(3) UNSIGNED would be the number of bytes it takes up, right?

Both would be 0-999.

[funkyprem]

Originally Posted by pgo

Both would be 0-999.

no mate, in paulantonys post the number in brackets is the range of numbers it can store. so a tiny int can't store a value of 257 and a smallint can't store 40,000 as they're both outside of thier respective ranges.