It's not open source; it's expensive; but the products from Embarcadero work
pretty well.
--
Scott Ribe
[EMAIL PROTECTED]
http://www.killerbytes.com/
(303) 722-0567 voice
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.pos
Christophe,
I agree with Dr. DeSoi that it may not always be possible to automate
schema transformations. However, if you need to compare the metadata
between two databases, the free, open-source SchemaCrawler for SQL
Server tool will do this for you. You can take human-readable
snapshots of the s
On Apr 22, 2008, at 4:33 PM, John DeSoi wrote:
On Apr 22, 2008, at 4:53 PM, Erik Jones wrote:
It would be nice if PostgreSQL had some kind of unique reference
for the column, but I think columns are just numbered sequentially
as they are added. It would also be neat to have a built-in way
On Apr 22, 2008, at 4:53 PM, Erik Jones wrote:
It would be nice if PostgreSQL had some kind of unique reference
for the column, but I think columns are just numbered sequentially
as they are added. It would also be neat to have a built-in way to
log the schema changes.
It does: log_state
On Apr 22, 2008, at 3:09 PM, John DeSoi wrote:
It would be nice if PostgreSQL had some kind of unique reference for
the column, but I think columns are just numbered sequentially as
they are added. It would also be neat to have a built-in way to log
the schema changes.
It does: log_state
).
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kerri Reno
Sent: April 22, 2008 8:44 AM
To: Christophe
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Schema migration tools?
Christophe -
We use LiquiBase: http://www.liquibase.org/home
We don't use it quite the
On Apr 21, 2008, at 10:44 PM, Christophe wrote:
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
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.
On Apr 21, 2008, at 7:44 PM, Christophe 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
Christophe wrote:
Greetings,
Does anything like this exist? If not, I might have a new project...
Typically new projects are found over at www.pgfoundry.org. :P
Joshua D. Drake
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://
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
11 matches
Mail list logo
