rafaelfranca/rails — comment on commit a967ac9be270184d3ca821e7a92366268c4482eb
File:  line 0
By victusfate:

just to clarify @rafaelfranca , It used to work in error in rails 2.3.4-3.1.3 but a change/bug fix in 3.2 reveals an error in my tables?
I can just migrate created_at away from the keywords_users table, but I'm not sure I remember how. Originally I added or dropped model members in migrations
add_column(table_name, column_name, type, options)
remove_column(table_name, column_name)

Then somewhere between 2.3.4 and a post 3.x version I changed those migrations to change calls.
change_column(table_name, column_name, type, options)

Which simplified my migrations files some.

So all I have to do now is create a new migration with:
remove_column('keywords_users', 'created_at')