Re: Schema version control

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: Andy Colson <andy(at)squeakycode(dot)net>
Cc: Royce Ausburn <royce(dot)ml(at)inomial(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Schema version control
Date: 2011-02-10 22:50:14
Message-ID: 20110210175014.ade7ec7a.wmoran@potentialtech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In response to Andy Colson <andy(at)squeakycode(dot)net>:

> On 2/10/2011 4:18 PM, Bill Moran wrote:
> >
> > We have this kickass solution we built at work called dbsteward that
> > just takes care of all of this for us, automatically. You just give
> > it the new version and the old version and it generates update statements
> > to feed into PG.
> >
> > The reason I'm bringing this up is that we're working to release
> > dbsteward as open source for PGCon. So, if you can wait a bit, you
> > can jump on that train.
> >
> > In response to Andy Colson<andy(at)squeakycode(dot)net>:
> >
>
> But... that assumes all updates are DDL only? What if I have a lookup
> table, and want to add some new entries into it?

It has provisions for maintaining static data as well. We have a bunch
of lookup tables (too many, in my opinion) and it does an excellent job
of maintaining them. They just need to have a primary key, but that's
not usually a problem with lookup tables.

--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2011-02-10 22:59:13 Re: Schema version control
Previous Message dennis jenkins 2011-02-10 22:45:16 Re: finding bogus UTF-8