| From: | Jim Nasby <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Jeff Amiel <jamiel(at)istreamimaging(dot)com> |
| Cc: | postgresql(at)teska(dot)net, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: how to update structural & data changes between PostgreSQL |
| Date: | 2006-03-23 17:41:07 |
| Message-ID: | 640E98AD-15D2-40EF-B7FF-93778E909FD4@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mar 22, 2006, at 9:21 PM, Jeff Amiel wrote:
> We have a fairly 'good' process at our shop that we follow that
> works for us....
>
> First we do a schema comparison between our prod and devl/test
> environments using the EMS PostgreSQL database comparer tool...
Another way to handle this is to keep your database code in a version
control system and tag each release. That way you can generate a diff
between two releases to see what's changed.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2006-03-23 17:51:39 | Re: Enforcing serial uniqueness? |
| Previous Message | Jim Nasby | 2006-03-23 17:37:03 | Re: How to release locks |