5 ms·
If you have giant migration scripts, for whatever reason, this tool is the only migration engine that would not choke on them.
by synchrone 6y ago
If you have giant migration scripts, for whatever reason, this tool is the only migration engine that would not choke on them.
- grey-area 6y agoReally? There are lots of tools out there which just rely on the db to run migrations.
- synchrone 6y agoI tried flywaydb, and some others. There are not a lot of migration tools that are not part of a bigger framework. Can you link some examples that you think would gladly process data-migrations that are 1-2GiB large?
- grey-area 6y agoAnything which doesn't try to process the sql file but instead just passes it to the db to deal with, e.g. psql -d mydb -f migration.sql I use a home-built solution that does this (160 lines of go), doesn't seem very exotic to me and did not require lots of work as there are only a few requirements for a working solution: Unique ordered names for migration sql files, use the db to store metadata about migrations run, use the db tools to run migrations.