Ruby on Rails

oh ok, I didn't realize that.

I do have one migration that I need to run that alters the name of the field in a table.  I accidentally capitalized the first character, and it caused all sorts of issues.  I can't seem to run that migration. 

Thanks,

Joe

On Tue, Sep 5, 2017 at 12:02 PM, Norbert Melzer <timmelzer@gmail.com> wrote:

On 09/05/2017 05:51 PM, Joe Guerra wrote:
> the database isn't in production, it has a bunch of faker data in it.

I do not care… You are taking huge risks by changing old migrations and
re-running from scratch. This way you might have deleted to much and
therefore your model might get out of sync with the table.

While when you add a single migration which is responsible to clean up
your schema, you can easily roll it back if you realise that it didn't
work as expected. This way back is not easily possible when you alter
your migrations history.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/4f3e88cf-8614-8aca-a614-9308eb653b34%40gmail.com.

For more options, visit https://groups.google.com/d/optout.