Show HN: Version Control for Databases
There are multiple tools that attempt to do this, some specific to a framework some not. To name a few,<p>- flyway<p>- liquibase<p>- dbmate<p>- alembic for python/sqlalchemy<p>- django migrations for python/django<p>- diesel migrations for rust/diesel<p>- echo migrations for elixir/echo<p>- persistent migrations for haskell/persistent<p>All of these, in one way or another, provide an ability to create sequential database schema changes that can be stored in version control and applied/rolled back.<p>What is your system doing that is different from all of these?