On Wed, Apr 7, 2010 at 1:10 PM, GoodGets <[email protected]> wrote: > So as long as I rake db:migrate:down and delete the migration file > from my local machine, the production database on the server when it > does go live (I haven't launched the app yet) will have no knowledge > of this migration having ever existed, right? > > because that's all I really care about, and I believe this is true, at > least from from my understanding now > > Thank you again Ryan
HA! My only contribution here was to miss the explanation badly enough to motivate Rick to write a longer and actually correct one. :) > On Apr 6, 11:53 pm, Ryan Waldron <[email protected]> wrote: >> It is in whatever database your app is using. Rails creates and >> maintains it for you. So if your production database is 'foo_prod', >> there would be a 'schema_migrations' table there, as well as in your >> 'foo_dev' development database. >> >> I don't know of a simple way to remove that row without firing up your >> database itself (MySQL or whatever). >> >> >> >> On Tue, Apr 6, 2010 at 10:43 PM, GoodGets <[email protected]> wrote: >> > Thanks Ryan >> >> > and, I hope this isn't too stupid of a question, but where is this >> > 'schema_migrations' table? >> >> > On Apr 6, 11:29 pm, Ryan Waldron <[email protected]> wrote: >> >> 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 <[email protected]> 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 [email protected]. >> >> > To unsubscribe from this group, send email to >> >> > [email protected]. >> >> > For more options, visit this group >> >> > athttp://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 [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group >> > athttp://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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
