Closed TimoKramer closed 1 year ago
@fpischedda I am thinking since you wished for a way to avoid conflicting schema migrations with colleagues that we could have something like a tool that tracks the migrations in a separate file. Then you would get merge conflicts in case you didn't rebase the last commit to this tracking file. @kordano came up with the idea, there is a tool called atlas for sql-dbs that does this already.
Hi @TimoKramer
This is a neat idea! I will also have a look at atlas, it could be useful at $work, thanks @kordano for mentioning it 🙂
I think there is something missing in the documentation that describes in which cases it makes sense to use norms for schema migration. For someone that hasn't read the conversation in this issue it doesn't become quite clear why you would need to have norms installed for something that would need to be done only once, naively assuming you only have one database of a kind.
SUMMARY
Checks
Feature
fixes #number