Top Nine Coding Guidelines for Oracle PL/SQL

Coding By Builder

My take, as of November 2015, of some of the most helpful guidelines to follow when writing PL/SQL code:

1. MAXSQL – maximize use of SQL first and foremost
2. SPOD – single point of definition
3. TRACE – production-available application-level tracing
4. LOG – consistent, encapsulated error logging
5. BULK – avoid row by row
6. OBVIOUS – make your code tell its own story, comment when it can’t
7. NESTPROG – use nested subprograms
8. DECLARE – use declarative features of language
9. WARN – use compile-time warnings

Accompanying blog post: http://stevenfeuersteinonplsql.blogspot.com/2015/10/your-ideas-for-more-important-plsql.html

========================================
Practically Perfect PL/SQL with Steven Feuerstein

Copyright © 2015 Oracle and/or its affiliates. Oracle is a registered trademark of Oracle and/or its affiliates. All rights reserved. Other names may be registered trademarks of their respective owners. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the “Materials”). The Materials are provided “as is” without any warranty of any kind, either express or implied, including without limitation warranties or merchantability, fitness for a particular purpose, and non-infringement.

========================================
Practically Perfect PL/SQL with Steven Feuerstein