From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | Alexey Bashtanov <bashtanov(at)imap(dot)cc> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: what database schema version management system to use? |
Date: | 2016-04-06 23:24:26 |
Message-ID: | 20160406192426.98cffc0a17fcb21a895fa76a@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 6 Apr 2016 11:55:40 +0100
Alexey Bashtanov <bashtanov(at)imap(dot)cc> 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?
--
Bill Moran
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2016-04-07 01:17:10 | Re: database is not accepting commands to avoid wraparound data loss in database |
Previous Message | Tom Lane | 2016-04-06 23:01:04 | Re: pg_upgrade error regarding hstore operator |