Hi, ime trying to get my head around how these interact as I acidentely deleted a migration and had not commited it to git.
The migration is ‘up’. So I did some research and it seems if I just
delete the migration from the schema_migrations (and make sure the corresponding database object does not exist) will fix it. So I had a look at scema_migrations table and this got me wondering how rails knows
if the migration is up or down, there is not status attribute on the table.
So I did some more research and came across db/schema.rb, which rails
used to work out if a migration is up or down. I looked in log/development.log to doble check what the migration was doing and found 'CREATE TABLE “create_report_upcoming_events” so I checked db/schema.rb and sure enough there is a reference to the view. This is not domething I want and it has not been put into production. So it seems if I just delete the record from the scema_migrations table things
will still be inconsistent.
So do I delete the row from schema_migrations and the reference to the view in db/schema.rb or will just deleting the migration from scema_migrations sufice?