versioning stored procedures/PLSQL?
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.
Update
Link to blog now is AMIS TECHNOLOGY BLOG
The following link no longer works
http://technology.amis.nl/blog/846/plsql-source-code-control-inside-the-database-after-compile-trigger-for-automatic-archiving
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...
We built a tool so that we can manage our PL/SQL code in the Oracle Database. It hooks Git to the Oracle database and helps you manage your PL/SQL code base easily. You can do basic Git tasks such as commiting, resetting, branching, cloning, merging, pulling etc... and Gitora automatically updates the PL/SQL code in the database.
You can download it at www.gitora.com.