RE: Stored Procedure Best Practices

Start this document with one line:

• decide for which version of Oracle Database you will develop

The point is that Oracle's stored procedures depend on Oracle version. What is written for older versions will run unmodified (almost, see bellow) on newer versions but not the other way around. The only forward compatibility issue that I know was about default values for arguments which is easy to fix and once fixed it is backward compatible.

In the other words both stored pl/sql language and available libraries are subject to change quite a lot. This is not like C/C++ where you can upgrade your compiler, add new libraries and the code you compile still runs on your platform of choice. New Oracle Database basically means a new platform. It proved to be extremely backword compatible (as far as stored procedures are concerned) but not the other way arround. BTW, I skipped the topic that new features usually do not work as advertised. This is something known by default.

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Guerra, Abraham J I am writing a stored procedure best practice document. If anyone has already written something to that effect, can you share it with me so I don't have to re-invent the wheel?

Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer

--
http://www.freelists.org/webpage/oracle-l