Re: what database schema version management system to use?

From: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: what database schema version management system to use?
Date: 2016-04-06 11:34:01
Message-ID: 5704F429.8060304@matrix.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 06/04/2016 13:55, Alexey Bashtanov wrote:
> Hi all,
>
> I am searching for a proper database schema version management system.
>
> My criteria are the following:
> 0) Open-source, supports postgresql
> 1) Uses psql to execute changesets (to have no problems with COPY, transaction management or sophisticated DDL commands, and to benefit from scripting)
> 2) Support repeatable migrations (SQL files that get applied every time they are changed, it is useful for functions or views tracking).
>
> Reasonable?
>
> But unfortunately it looks like each of Liquibase, Flyway, SqlHawk, MigrateDB, Schema-evolution-manager, Depesz's Versioning, Alembic and Sqitch does not satisfy some of those, right?
>
> What DB VCS do you use and how does it related with the criteria listed above?
> Do you have any idea what other systems to try?

Maybe Git then interface with smth like teamcity to apply your changes. Honestly you are asking too much. The classic problem is to find a tool that would translate DDL diffs into ALTER commands, if
you want to store pure DDL CREATE statements. I have watched many presentations of people on the same boat as you, and they all implemented their own solutions. Good luck with your solution and keep
us posted, many ppl might benefit from this.

>
> Regards,
> Alexey
>
>

--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2016-04-06 13:50:08 Re: Exclude constraint using custom operator
Previous Message sgringer 2016-04-06 11:02:31 PostgreSQL 9.5.1 -> PG_REWIND NOT FOUND