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@xxxxxxxxxx]
Sent: Wednesday, October 24, 2007 10:24 PM
To: pgsql-general@xxxxxxxxxxxxxx
Cc: Roberts, Jon
Subject: Re: 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@xxxxxxxxxxxx>
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@xxxxxxxxxxxxxx so that your
message can get through to the mailing list cleanly
