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,- flyway- liquibase- dbmate- alembic for python/sqlalchemy- django migrations for python/django- diesel migrations for rust/diesel- echo migrations for elixir/echo- persistent migrations for haskell/persistentAll 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.What is your system doing that is different from all of these?