From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
---|---|
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-26 14:43:30 |
Message-ID: | 4721FD12.1030504@wildenhain.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Dave,
Dave Page schrieb:
>
>> ------- Original Message -------
>> From: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
>> To: pgsql-general(at)postgresql(dot)org
>> Sent: 25/10/07, 17:35:32
>> Subject: Re: [GENERAL] subversion support?
>>
>> 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.
But it was implemented differently then the proposal above.
One way to implement it as easily as possible would be the ability
to link editor windows to file on disk, where you could have
the file version controled and changes to the file would show
up immediately in the edit window where edits in the window
could (with small delay) auto saved to the file.
This way you need not change pgadmin much while you can use cvs/svn
on your file system to do the VC stuff.
"only" a clever way for mapping (maybe based on object type)
configuration and the change detection (file notify, FAM, ...)
(the latter depending on the OS unfortunately)
Regards
Tino
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2007-10-26 14:49:59 | Re: select count() out of memory |
Previous Message | Vince Negri | 2007-10-26 13:38:49 | Re: TRUNCATE - timing of the return of disk space - caused by long-lived client? |