Is there an efficient way to version store procedures written in PL/SQL? (I only mention PL/SQL because there may exist a particular tool, any answer directed to versioning of stored procedures is ideal).
+2
A:
Can you use a 'regular' version control system? All of our deployed/deployable stored procs are controlled just like application code.
It's been a while since I've dealt with PL/SQL, so I don't have anything to offer on the package definitions.
Granted, this isn't in the database, but...
DaveE
2010-03-05 23:04:50
+3
A:
In my current job , the team is now using the following method to version control the PL/SQL .When compiling the PL/SQL , no matter compile successfully or not , a record will be inserted into the log table . Besides in the mid-night , there is an JAVA agent to be scheduled to run automatically check if the PL/SQL source needed to check into the CVS.
We employ a similar system to this at my job as well. My main issue with it is that there's not much info to go with the check-in. We can't tell what code changes relate to which issue in our bug-tracking system. There's no "why" when we look at the history, just users and dates. Also, there's a lot of noise, as the incomplete work gets a check-in as well. We haven't found a good way to deal with these things.
Adam Hawkes
2010-03-13 01:22:31
+1
A:
Oracle's free SQL Developer tool has integration with CVS and Subversion for version control of PL/SQL code.
Tony Andrews
2010-03-06 10:56:25