On Sat, Mar 26, 2016 at 4:35 AM, Colin L. [email protected] wrote:
It is best to add a new migration to do this.
((this is what I tried to send))
Agreed. If you change an old migration, and run
will happen, because that migration is already saved in the database
‘schema_migrations’. You either need to create a new migration, or you
to drop the data base and re-run all the migrations.
I once tried to circumvent this in a panic situation by deleting the
migration record and re-running the migration, but it was such a crazy
thing to try, I gave up.
My advice is to do just as Colin suggested, and use a new migration to
change the table.