Re: [Rails] Re: URGENT + production migrations

On 27 May 2010 15:15, anon_comp <neocoolstar@gmail.com> wrote:
> I know this has already been resloved, but instead of creating a new
> migration, you could have gone back to version 0
>
> rake db:migrate VERSION=0
>
> then run rake db:migrate
>
> this should update all migrations you edited.

The downside is that migrations will often have a create_table in the
up method and a drop_table in the down method. As Hemant said this
was on a production system, doing as you suggest would lose all his
live/production data.

Probably not the solution he'd desire :-)

Cheers,

Andy

--
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-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.