- All variable names should start with “v”. e.g., vKount Number;
- All stored procedure names should start with “SP_”.
e.g., Create or Replace Procedure SP_HPC_Cashback(OutMsg Out VarChar2) is - All stored function names should start with “SF_”.
e.g., Create or Replace Procedure SF_CalcInt(Prin Number, Yr Number) return number is - All package names should start with “PKG_”.
e.g., CREATE PACKAGE PKG_DMR_Processing as - All Procedures should have a parameter as “OutMsg Out VarChar2” which should be used for returning the success of error message to the caller methods.
e.g., Create or Replace Procedure SP_HPC_Cashback(OutMsg Out VarChar2) is - Never use ORACLE keywords like count, name, date, time, etc. as table fields’ name.
- Do maintain TO DO LIST to keep track of the pending tasks with you. If possible, maintain it using Excel.
- The SQL queries & PL/SQL source code both should be well indented as shown in the document above.
- The lines should not extend 80 characters in length. This will help making code printer friendly and easy to understand.
- Avoid unnecessary multiple blank lines.
- Code should be adequately commented.
- If modifying existing code, then mention the date of modification along with the name of the modifier & the reason for the modification with the “Change Request Number” in the comments.
- Make a habit of writing the detailed caution for the risky code statements wherever applicable.
- Exception handling to done wherever necessary.
- Make a habit of documenting each details of the project to avoid confusion. Create documents like flow charts, Project Requirements, Test logs, etc.
- Review the documentation done regularly to keep it up to date.
- Backup your code regularly using tools like Team Source or SVN, if available else backup your code manually.
- After completing unit test, get the developed program reviewed & tested by your peer, if possible.
- Get the requirements over the mail from the client (Internal / external). If you are unable to get it then you put it in writing and send them the details before starting the work.
All about Oracle SQL & PL/SQL
TechOraFAQ 