Re: 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.

And no, I will not sponsor such development.

Jon
-----Original Message-----
From: Joshua D. Drake [mailto:jd(at)commandprompt(dot)com]
Sent: Thursday, October 25, 2007 11:16 AM
To: Roberts, Jon
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] subversion support?

Roberts, Jon wrote:
> I could use psql instead of pgAdmin then which isn't what I want.
>
> Having used Quest software SQL Navigator since 97 for Oracle and then
> migrated to Toad for Oracle which both products have integration to source
> control, it is hard to revert back to a command line or text file
solution.
>
>
> pgAdmin should graphically show differences between the committed version
> and the database.

1. Complaints about pgadmin, should go to the pgadmin this. This is a
postgresql list.

>
> It should allow me to click a button in the tool and commit it to the
> repository.
>
> It should allow me to revert back to a previous version and the tool take
> care of restoring the function automatically.
>
> It should show history and let me see the differences.
>
> In other words, take Tortoise and merge that product into pgAdmin so I
have
> one product instead of two.

2. Are you will to sponsor such development?

Sincerely,

Joshua D. Drake

>
>
> Jon
>
> -----Original Message-----
> From: Brad Lhotsky [mailto:lhotskyb(at)mail(dot)nih(dot)gov]
> Sent: Thursday, October 25, 2007 9:13 AM
> To: Roberts, Jon
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] subversion support?
>
> You could setup a subversion commit hook to export the functions to the
> database.
>
> Then you adjust your development mentality to:
>
> 1) Edit the files on the disk
> 2) Commit to Subversion
>
> Then the hook takes over and runs the drop/create automatically, you
> could even have it email the developer if the create failed.
>
>
> Roberts, Jon wrote:
>> Robert, that does sound better. It keeps the names of the files in svn
>> consistent with the database object names which is essential. It also
> makes
>> it automatic. Unfortunately, it doesn't tell you who did the changes.
>>
>> Do you want to share that code?
>>
>>
>> Thanks!
>>
>>
>> Jon
>>
>> -----Original Message-----
>> From: Robert Treat [mailto:robert(at)omniti(dot)com]
>> Sent: Wednesday, October 24, 2007 10:24 PM
>> To: pgsql-general(at)postgresql(dot)org
>> Cc: Roberts, Jon
>> Subject: Re: [GENERAL] subversion support?
>>
>> On Wednesday 24 October 2007 15:11, Roberts, Jon wrote:
>>> Yeah. I think having to save the function to disk and then leave
pgAdmin
>>> to execute subversion commands is going through hoops.
>>>
>>> Also, pgAdmin should be integrated so that you are notified if the
>> function
>>> in the database is different from the last committed version. A visual
>>> diff should be there so you can see what the differences are.
>>>
>> We have a script that runs nightly that dumps tables / functions to file,
>> and
>> then checks it in automagically to svn, which sends an email of the
diffs.
>
>> Perhaps that would work for you?
>>
>