Re: subversion support? - Mailing list pgsql-general

I not sure I follow the question about SQL Navigator and Toad.

When you edit a function, package, procedure, trigger, etc, it will notify
you via a pop-up window if there is a difference in the committed version
and the database version.  You can then click "show differences" and then it
pops up another window with your typical code differences window.

When you are done revising the code, you then commit it to the repository in
the tool with a click of a button.

So the long story short I'm getting is, "no it is not on the radar".  This
is terribly ironic given the fact that pgAdmin is developed using source
control but the code you write with the tool doesn't have any hooks into
source control.


Jon

-----Original Message-----
From: Tino Wildenhain [mailto:tino@wildenhain.de]
Sent: Thursday, October 25, 2007 11:03 AM
To: Roberts, Jon
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] subversion support?

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