Owain wrote: > rake RAILS_ENV=staging db:drop > rake RAILS_ENV=staging db:create > rake RAILS_ENV=staging db:migrate
RichardOnRails wrote: > That's easier than the three-stage solution you used, though > equivalent in effect I believe. For what it's worth the "three-stage solution" can be done with one rake task: rake RAILS_ENV=staging db:migrate:reset However, the change_column approach seems the safer and cleaner solution. This technique keeps the migrations moving forward. Given that dropping, recreating and migrating fixed your problem this leads me to this question, "Was the precision and scale explicitly configured in the migration before running the migrations? -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
