Dave,
Thanks for the quick feedback. I'm really surprised that people who use
VCS for their 'normal' code, wouldn't see a use for the same when it
comes to DB Schema/DDL versions.
In any case, my goal is not to add the functionality directly to
PGAdmin, but rather create a plugin for PGadmin to use.
As I mentionned earlier, the extent of the modifications to PGadmin
would be to extend the plugin framework to allow a tighter coupling
between plugins and PGadmin.
I guess maintaining a plugin is different from maintaining yet another
feature in the existing PGAdmin code, correct me if i'm wrong.
Finally, since no one wanted to use the VCS feature in PGadmin, what do
teams of developers use to track versions of Schemas (Tables, Views,
Procedures...)?
Do most developers simply not use any? Or do the 'hack' their own? I'd
be surprised if they used proprietary tools ...
On 15/12/2011 10:17 AM, Dave Page wrote:
> On Wed, Dec 14, 2011 at 6:27 PM, David Vaillancourt
> <david_v@sympatico.ca> wrote:
>> Hi,
>>
>> I would like to start implementing a version control system to be used
>> to track Schema/DDL changes for a DB.
>> I have compiled and run Pgadmin iii on my computer and figured the
>> current plugin architecture would not be a perfect fit for this new feature.
> We had version control for database objects in pgAdmin II - when we
> started on pgAdmin III, a survey revealed it was a feature that
> literally no one (except me at the time) wanted.
>
> I'd be very wary of accepting code to implement such functionality
> again, unless there were others who saw benefit in it, and it was
> going to be relatively low maintenance in the long term.
>
