3 ms·
Dumb question here. Instead of keeping all these migration files why can the migration just compare the models to the database directly and make he appropriate
by tocomment 13y ago
Dumb question here. Instead of keeping all these migration files why can the migration just compare the models to the database directly and make he appropriate changes?
- jsmeaton 13y agoFor a couple of reasons that I can think of. You might want to do a rollback. You may have multiple copies of the database (various dev versions, staging, production), and multiple changesets might build up in one environment before progressing to another which must be specifically ordered. There may be changes that need to be manually coded or tweaked, and you need some intermediate structure for that to happen.