If youre looking for a PHP solution, theres:
Its very limited but works for simple schemas, I begun extending it to
support more rigorously SQL-92 schema information (will be released BSD
license at openmv.com).
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Kerri Reno
Sent: April 22, 2008 8:44 AM
Subject: Re: [GENERAL] Schema migration tools?
We use LiquiBase: http://www.liquibase.org/home
We don't use it quite the same as what you're proposing, but I think you
could use it that way. When we found it, we did 'Generate Changelog' to
start, then made new changes to the ChangeLog, and applied it to each
database as needed. It has really helped us, because we were forgetting to
apply the changes to the production database that were needed.
Hope this helps!
On 4/21/08, Christophe <xof(at)thebuild(dot)com> wrote:
We have the traditional three servers:
dev --> staging --> production
each with a PostgreSQL instance and the same schema, at least over time.
Right now, we handle schema migration (updating the schema for new releases)
by manually-created scripts that apply the changes to staging and
I'd like a tool that would automatically create these scripts, and I
wondered if anything like this existed. The theory would be that it would
consider two databases a and b, and produce the appropriate script to change
b's schema to match a.
Does anything like this exist? If not, I might have a new project...
Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
To make changes to your subscription:
Yuma Educational Computer Consortium
Compass Development Team
kreno(at)yumaed(dot)org (928) 502-4240
.·:*¨¨*:·. .·:*¨¨*:·. .·:*¨¨*:·.
In response to
pgsql-general by date
|Next:||From: D. Dante Lorenso||Date: 2008-04-22 20:45:39|
|Subject: Re: How to modify ENUM datatypes?|
|Previous:||From: Scott Marlowe||Date: 2008-04-22 20:38:29|
|Subject: Re: Rapidly decaying performance repopulating a large table|