Trivadis PL/SQL & SQL Coding Guidelines v4.1
Version 4.1
https://trivadis.github.io/plsql-and-sql-coding-guidelines/v4.1/
PLSQL-and-SQL-Coding-Guidelines.pdf
New
- #120 - Added new rule G-7910: Never use DML within a SQL macro.
- #23 - Added new rule G-3220: Always process saved exceptions from a FORALL statement.
- #49 - Added new rule G-4365: Never use unconditional CONTINUE or EXIT in a loop.
- #46 - Added new rule G-3145: Avoid using SELECT * directly from a table or view.
- #100 - Added new rule G-9040: Try using FX in string to date/time conversion format model to avoid fuzzy conversion.
- #111 - Formatted all examples according to coding style in our guidelines.
- #111 - Added automatic formatting of examples using git hook.
Changed
- #8 / #9 - Restructured Tool Support section with individual chapters on 4 db*CODECOP tools as well as plscope-util.
- #103 - Unique subchapters per rule and consistent order.
- #117 - Consistent handling of the Oracle database version.
- #122 - Consistent case of the word Oracle.
- #114 - G-7730: Clarify scope.
- #105 - G-4220 violates rule G-1050 in bad and good example.
- #91 - G-7730 valid in all cases or only if PK is assigned.
- #109 - Update images, logos, favicon, etc. due to acquisition of Trivadis by Accenture leading to updated corporate design.
Fixed
- #106 - Appendix B: Old ID 68 -> New ID 7160.
- #104 - Bad example in G-4210 violates rule G-2130 in line 2.
- #116 - G-9020/G-9030: syntax error in good and bad example.
- #115 - G-9010: syntax error in good and bad example.
- #113 - G-7330: Wrong procedure label in bad and good examples.
- #112 - G-7810: Fix typo in SQL.
- #102 - G-2230: Add deterministic keyword to avoid violating G-7460.
- Fixed typos in G-7310 and G-7410.