Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I made a rookie mistake with a migration yesterday. I amended a migration that had already been uploaded and run, and I forgot to rollback before uploading the new version. Now, the migration is failing because either a column already exists (up) or there is no column to delete (down)!
Is it possible to get a migration to force its changes one time from the console, without having to write :force => true within the document first, migrating, and then removing it again?
A simple way of getting back to a stable state would be to make a manual change in the database adding the column so that the rollback works, and then do the rollback and migrate up again.