Is there a reason the ActiveRecord MySQL adapater uses signed integers for the primary key field? It's a relatively minor issue, but it seems unnecessary and inefficient. I didn't want to submit a patch if there's a reason it's there though
I was also considering a patch adding a 'foreign_key' type, since essentially the same issue exists when using the integer type for foreign key fields