Malformed migrations result in odd column names

Hello,

I took a look at this and based on the above I was able to replicate this.

a) created a model named foo
b) updated the migration to do the following:

create_table :foos do |t|
t.integer :node_id, t.timestamps end

c) ran rake db:migrate, looked at the database and found this:

| node_id | int(11) | YES | | NULL | | | #<ActiveRecord::ConnectionAdapters::TableDefinition:0x10317a080> | int(11) | YES | | NULL | |

d) this was tested against Rails 2.3.8.

Mike Riley
twitter.com/wdperson

Unfortunately this is a typo that happened and there is not much we can do about this.