You'll also need to remove that migration's entry from the 'schema_migrations' table. That's how Rails keeps up with what migrations exist, and whether it's done them all.
On Tue, Apr 6, 2010 at 10:10 PM, GoodGets <goodg...@gmail.com> wrote: > What exactly does rake db:migrate:down VERSION=XXX do? I understand > that it runs the "down" migration, completely removing any columns/ > tables that migration may have created, but does this mean that I can > can delete these migration files as well? I'd like for Rails to have > no knowledge of their existence. (I was allowing user profile pics > with Paperclip, but have since decided to just use their Gravatars.) > > I know you can delete a migration, and even delete those columns from > the schema, but Rails still "remembers" these changes and just updates > them the next time you rake db:migrate. So, I'd like to completely > rid my app of a particular migration, is rake db:migrate:down then > deleting that migration from the migrate folder the way to do it? > > -- > 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. > > -- 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.
