Christophe - 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! Kerri On 4/21/08, Christophe <[EMAIL PROTECTED]> wrote: > > Greetings, > > 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 > production. > > 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... > > Thanks! > -- Christophe > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > -- Yuma Educational Computer Consortium Compass Development Team Kerri Reno [EMAIL PROTECTED] (928) 502-4240 .·:*¨¨*:·. .·:*¨¨*:·. .·:*¨¨*:·.
