phsjhxx

More documents

Recommendations

Info

PL/SQL & SQL Coding Guidelines Trivadis AG Document Version 1.3.1 ©2010 Trivadis AG
Foreword Coding Guidelines are an important quality standard for any programming language. Not only that coding based on standards results in better software products, standards also help programmers to work in teams. These coding guidelines represent many years of experience – not only delightful ones - in constructing and maintaining PL/SQL and SQL programs. These programs are pieces of software to implement business logic in order to support high end data processing. Or in other words to get value out of one of the most important assets of a company - the company's information. From small functions to help to automate a database administrators work to complex frameworks for historization or other purposes. Many software products are programmed fully in PL/SQL or in SQL. I am convinced that these PL/SQL and SQL Coding Guidelines are a valuable contribution to enhance software quality and improve team performance. May the code be with you. Urban Lankes CEO Trivadis "Roger and his team have done an excellent job of providing a comprehensive set of clear standards that will undoubtedly improve the quality of your code. If you do not yet have standards in place, you should give strong consideration to using these as a starting point." Steven Feuerstein PL/SQL Evangelist Coding Guidelines are a crucial part of software development. It is a matter of fact, that code is more often read than written – therefore we should take efforts to ease the work of the reader, which is not necessarily the author. I am convinced that this standard may be a good starting point for your own guidelines. Roger Troller Senior Consultant Trivadis PL/SQL Coding Guidelines 2
Page 1: PL/SQL & SQL CODING GUIDELINES VERS
Page 5 and 6: Table of Contents 1. Introduction .
Page 7 and 8: 1. Introduction This document descr
Page 9 and 10: 3.2. Naming Conventions for variabl
Page 11 and 12: Identifier Package Naming Conventio
Page 13 and 14: 4. Coding Style 4.1. Formatting PL/
Page 15 and 16: Tag Meaning and Pattern Program Exa
Page 17 and 18: 4.2.1 IDE Templates Code Templates
Page 19 and 20: Example: -- Bad DECLARE l_function
Page 21 and 22: List of possible subtype definition
Page 23 and 24: 5.2.2 Numeric Data Types 18. Avoid
Page 25 and 26: 5.2.5 Large Objects 24. Avoid using
Page 27 and 28: -- Good DECLARE CURSOR c_user IS SE
Page 29 and 30: 31. Avoid procedure or function cal
Page 31 and 32: -- Good BEGIN l_result := CASE dumm
Page 33 and 34: 40. Always use a WHILE loop to proc
Page 35 and 36: 45. Avoid use of unreferenced FOR l
Page 37 and 38: 50. Avoid use of EXCEPTION_INIT pra
Page 39 and 40: 5.6. Dynamic SQL 54. Always use a s
Page 41 and 42: 58. Always use parameters or pull i
Page 43 and 44: 5.7.3 Functions 67. Avoid standalon
Page 45 and 46: 5.8.2 Access objects of foreign app
Page 47 and 48: 6.1.2 CodeXpert The calculation of
Page 49 and 50: 6.2. Cyclomatic Complexity (McCabe
Page 51 and 52: 7. Code Reviews Code reviews check
Page 53:
UNSERE STANDORTE BASEL BERN LAUSANN
show all

phsjhxx

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?