ruby schema generator generates int(11) when it should generate bigint(20) for 'ID's in MySQL

Wide enough for what? "100 Billion Should Be Enough For Everyone" :)

FYI, the width has nothing to do with the precision. It is only used, according to the mysql manual, "left-pad the display of values having a width less than the width specified for the column". Furthermore, "The display width does not constrain the range of values that can be stored in the column, nor the number of digits that are displayed for values having a width exceeding that specified for the column."

It's the actual column type that constrains the range of values. "int" (unsigned) has a range of 0 to 4,294,967,295. "bigint" has a range of 0 to 18446744073709551615. It might be desirable to allow the type of the "id" column to be changed (from "int" to "bigint", for example), but really... 4 billion is quite a bit. I can imagine there are apps that need a wider range, so I can see where a patch allowing the column type to be more flexibly specified would be desirable in some instances. If someone were to submit such a patch, it would probably be accepted.

My goof. I was more concerned about 'int' vs. 'bigint', and the lack of unsignedness.