| From: | Royce Ausburn <royce(dot)ml(at)inomial(dot)com> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Schema version control |
| Date: | 2011-02-11 03:06:17 |
| Message-ID: | E33B80F2-7020-43A3-B369-254C1D602D4A@inomial.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/02/2011, at 9:59 AM, Thomas Kellerer wrote:
> Royce Ausburn wrote on 10.02.2011 22:38:
>> I'm really interested to hear how you guys manage schema upgrades in
>> the face of branches and upgrading from many different versions of
>> the database.
>
> We are quite happy with Liquibase. You can simply run it against a database and tell it to migrate it to "Version x.y"
>
> As it keeps track of all changes applied it automatically knows what to do.
>
> I can handle static data as well as stored procedure and any custom SQL.
Thanks! Liquibase looks pretty neat. We'll have to check it out.
--Royce
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Royce Ausburn | 2011-02-11 03:08:25 | Re: Schema version control |
| Previous Message | Geoffrey Myers | 2011-02-11 01:40:34 | plsql question |