From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Dave Page" <dpage(at)postgresql(dot)org> |
Cc: | "Roberts\, Jon" <Jon(dot)Roberts(at)asurion(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: subversion support? |
Date: | 2007-10-25 18:06:12 |
Message-ID: | 87ve8v83xn.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Dave Page" <dpage(at)postgresql(dot)org> writes:
>> Complaint? Who is complaining?
>>
>> I am simply asking if this feature that is rather common in other database
>> development tools will ever be added to pgAdmin.
>
> pgAdmin II had change control. No-one ever really used it though so we never
> bothered to implement it in pgAdmin III.
Note that most database admins I've seen use change control by making a series
of sql files with all the definitions they need to recreate the tables. They
then use those sql files to drive the database, rather than the other way
around. So you just need to track those sql files in your revision control
system, and they're just plain text.
The situation is complicated somewhat by the SQL "ALTER TABLE" and so on
commands which you need to use instead of just reissuing the CREATE TABLE
command.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-10-25 18:23:20 | Re: subversion support? |
Previous Message | Magnus Hagander | 2007-10-25 17:55:35 | Re: subversion support? |