From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Steve Manes <smanes(at)magpie(dot)com> |
Cc: | PgSQL General ML <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: DDL diff utility? |
Date: | 2003-09-19 14:20:45 |
Message-ID: | 1063981246.30308.1673.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2003-09-19 at 07:42, Steve Manes wrote:
> My company offers an ASP service for advertising companies using PG.
> For contractual reasons, each client gets its own replicated database.
> This presents a problem whenever a new feature/fix requires a DDL change
> which must be rolled out across N databases. Currently, we keep track of
> these changes via a central text file in CVS with manually entered DDL
> updates. The problem is making sure that overworked developers actually
> log all these changes.
>
> What would be better is a DDL 'diff' utility that would look at a master
> and target database and generate the necessary ALTER statements needed
> to make the target db look like the master.
>
> Is anyone aware of such a tool for PG? I've only found it for MSSQL.
>
Check the mailing list archives, IIRC there is a project on sourceforge
that does this. It's a little weird though, I think it was written in
tcl and required a running webserver to make connections. HTH,
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-09-19 14:50:15 | Re: Why does adding SUM and GROUP BY destroy performance? |
Previous Message | Doug McNaught | 2003-09-19 14:11:22 | Re: Access Ingres database |