results

What do you think of the approach that pg_roll takes? Seems like the top contenders, at least for Postgres, are: sqldef: https://news.ycombinator.com/item?id=46845239 pgschema: https://github.com/pgschema/pgschema pg_roll: https://github.com/xataio/pgroll atlas: https://github.com/ariga/atlas grate (minimal SQL-based migrations): https://grate-devs.github.io/grate/ pg-schema-diff: https://github.com/stripe/pg-schema-diff results: https://github.com/djrobstep/results https://david.rothlis.net/declarative-schema-migration-for-s...

Personally I've always called this style "declarative schema management" since the input declares the desired state, and the tool figures out how to transition the database to that state. sqldef is really cool for supporting many database dialects. I'm the author of Skeema [1] which includes a lot of functionality that sqldef lacks, but at the cost of being 100% MySQL/MariaDB-specific. Some other DB-specific options in this space include Stripe's pg-schema-diff [2], results [3], stb-tester's migrator for sqlite [4], among many others over the years. The more comprehensive solutions from ByteBase, Atlas, Liquibase, etc tend to support multiple databases and multiple paradigms. And then over in Typescript ORM world, the migrators in Prisma and Drizzle support a "db push" declarative concept. (fwiw, I originated that paradigm; Prisma directl