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).
The answer is that PL/SQL is not growing, but not going away either. Because it is used in the Oracle database, and the Oracle database is a fixture of enterprise systems world-wide, it will outlive you. High-performance batch processing has to happen close to the data, so PL/SQL will continue to rule in this area.
There are two types of variable scope: Local Variable: Local variables are the inner block variables which are not accessible to outer blocks. Global Variable: Global variables are declared in outermost block.
A function cannot call the procedure inside the program's body.
Unlike a function, the procedure does not have any specific return type and doesn't return single but multiple values. Package: A package, which is a schema object, is responsible for grouping PL/SQL types, subprograms and items, which are logically related.
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.
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
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With