Re: what database schema version management system to use?

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Alexey Bashtanov <bashtanov(at)imap(dot)cc>, pgsql-general(at)postgresql(dot)org
Subject: Re: what database schema version management system to use?
Date: 2016-04-06 13:50:16
Message-ID: 57051418.8090303@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 04/06/2016 03:55 AM, 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?

I use Sqitch and supports the above afaict. The only one I would have a
question about is 2) as I am not quite sure what you are getting at.

>
> 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?
>
> Regards,
> Alexey
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2016-04-06 14:00:20 Re: Trying to understand page structures in PG
Previous Message Tom Lane 2016-04-06 13:50:08 Re: Exclude constraint using custom operator