3 ms·
And I assume you mean all of this is easier to do, safer, takes less effort, has more documentation, is more tested and proven and will be easier to understand
by midrus 6y ago
And I assume you mean all of this is easier to do, safer, takes less effort, has more documentation, is more tested and proven and will be easier to understand by a new joiner after the one that wrote it left than using an existing, popular solution?
Sorry, I disagree.
- gnud 6y agoJust use Dbup [1] if you're a .net shop, and flyway [2] otherwise. They are both existing, popular solutions that helps you organize your plain SQL migration scripts. 1: https://dbup.readthedocs.io/en/latest/ https://dbup.readthedocs.io/en/latest/ 2: https://flywaydb.org/ https://flywaydb.org/
- dgellow 6y agoIt’s definitely tested and proven, that’s a very common approach (not this specific migrate tool, but the general pattern). It’s simple to setup and only require standard SQL (or whatever your DB is using), has almost no moving parts, and is as stable as it can be. I’m not saying it’s easier than other solutions, that’s not really a criteria I personally care about. But it is stable, simple, relatively easy to maintain, using standard tools, reliable.