SEO

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.

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.


Jon

-----Original Message-----
From: Brad Lhotsky [mailto:lhotskyb@mail.nih.gov]
Sent: Thursday, October 25, 2007 9:13 AM
To: Roberts, Jon
Cc: pgsql-general@postgresql.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@omniti.com]
> Sent: Wednesday, October 24, 2007 10:24 PM
> To: pgsql-general@postgresql.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?
>

--
Brad Lhotsky <lhotskyb@mail.nih.gov>
NCTS Computer Specialist Phone: 410.558.8006
"Darkness is a state of mind, I can go where you would stumble."
-Wolfsheim, 'Blind'

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Hi,

Roberts, Jon schrieb:
> 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.

Well you can still use gui tools and just let them work against a
development database. With little scripting you can just dump
the schema of that database periodically and check it in to SVN.

Hook scripts can then take over the deployment (ideally based
on tag creation)

>
> pgAdmin should graphically show differences between the committed version
> and the database.

Does SQL Nav do this? At least the SQL Navigator/Toad support seems
to heavily depend on server side code to help. This looks very unclean
to the very least.

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

You can test before you commit in the database - unlike Oracle, Postgres
supports transactions even for DDL :-) (ok, I've yet find the button
in pgadmin to disable auto commit :-)


Regards
Tino

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

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@mail.nih.gov]
> Sent: Thursday, October 25, 2007 9:13 AM
> To: Roberts, Jon
> Cc: pgsql-general@postgresql.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@omniti.com]
>> Sent: Wednesday, October 24, 2007 10:24 PM
>> To: pgsql-general@postgresql.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?
>>
>


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Ever tried Druid?

http://druid.sourceforge.net/


Il Thursday 25 October 2007 18:02:51 Tino Wildenhain ha scritto:
> Hi,
>
> Roberts, Jon schrieb:
> > 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.
>
> Well you can still use gui tools and just let them work against a
> development database. With little scripting you can just dump
> the schema of that database periodically and check it in to SVN.
>
> Hook scripts can then take over the deployment (ideally based
> on tag creation)
>
> > pgAdmin should graphically show differences between the committed version
> > and the database.
>
> Does SQL Nav do this? At least the SQL Navigator/Toad support seems
> to heavily depend on server side code to help. This looks very unclean
> to the very least.
>
> > 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.
>
> You can test before you commit in the database - unlike Oracle, Postgres
> supports transactions even for DDL :-) (ok, I've yet find the button
> in pgadmin to disable auto commit :-)
>
>
> Regards
> Tino
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org/