| From: | "Dave Page" <dpage(at)postgresql(dot)org> |
|---|---|
| To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | "Roberts\, Jon" <Jon(dot)Roberts(at)asurion(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: subversion support? |
| Date: | 2007-10-25 19:11:06 |
| Message-ID: | 200710252011070000@132355196 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> ------- Original Message -------
> From: Gregory Stark <stark(at)enterprisedb(dot)com>
> To: "Dave Page" <dpage(at)postgresql(dot)org>
> Sent: 25/10/07, 19:06:12
> Subject: Re: subversion support?
>
> The situation is complicated somewhat by the SQL "ALTER TABLE" and so on
> commands which you need to use instead of just reissuing the CREATE TABLE
> command.
From memory, pga2 used to log the reverse engineered DDL after a change, as well as the SQL used to make that change. It then allowed you to generate scripts to update your production schemas from one version to another. It also allowed you to view the history for an object, and rollback to a previous version. Dropped objects were logged in the 'graveyard' from where they could be resurrected.
/D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-25 19:24:08 | Re: 2 versions running & using pg_dumpall |
| Previous Message | Scott Marlowe | 2007-10-25 18:23:20 | Re: subversion support? |