4 ms·
a .sql migration file is like a .tf terraform file, it describes intent your infrastructure is not that .tf definition, it's whatever is currently deployed to
by preseinger 4y ago
a .sql migration file is like a .tf terraform file, it describes intent
your infrastructure is not that .tf definition, it's whatever is currently deployed to ec2
in the same way, your schema is not that .sql file, it's whatever the database says it is :)
- winrid 4y agoI don't really get your point. Yes, the db validates the requests. But that's based off the schema. The schema is determined from the migrations. You run the new migrations before any deploy. You can keep pushing this argument but it doesn't mean anything in any practical sense.
- preseinger 4y agomy point is basically this: when the code in your application interacts with the DB, and it encounters a (runtime) error from a mismatch between the app's understanding of the DB schema and the DB's understanding of the DB schema, is that error handled gracefully? if yes, good! if no, because the app code assumes this is somehow impossible, that's a problem. that's all.