Trivadis PL/SQL & SQL Coding Guidelines v3.4
Version 3.4
https://trivadis.github.io/plsql-and-sql-coding-guidelines/v3.4/
PLSQL-and-SQL-Coding-Guidelines.pdf
New
- #55 - Added naming conventions for check constraints (
_ck
suffix) - #56 - Added section "We do not agree with all your standards" in introduction chapter
- #56 - Added footnote for tables, views; explaining why we use plurals in naming conventions chapter
- #56 - Added footnote for indention; explaining why we use 3 spaces in coding style chapter
- #70 - Extended naming conventions for views and tables regarding EBR (
_eb
suffix)
Improved
- #4 - Renamed the use of "ANSI-join" to "ANSI SQL-92 join" (title and reason in G-3130)
- #7 - Renamed G-8420 to G-8510 to follow numbering rules (new chapter)
- #14 - Do not wrap lines in code blocks on devices with small screen widths
- #61 - Add explanation to good example of G-3150 regarding
GENERATED ALWAYS AS IDENTITY
- #62 - Renamed G-3160 from
"Avoid virtual columns to be visible" to
"Avoid visible virtual columns" - #63 - Add char semantic in column of G-3170
- #64 - Improved formatting of bad example in G-4220 (
decode
) - #67 - Renamed G-8410 from
"Always use application locks to ensure a program unit only running once at a given time" to
"Always use application locks to ensure a program unit is only running once at a given time" - Updated Trivadis logo (without slogan "makes IT easier")
Fixed
- #18 - Example uses one parameter, G-7110 is applied only for two and more parameters
- #20 - Added missing
G-
prefix in G-7320 - #21 - Incomplete good and bad examples in G-8410
- #65 - Broken link in G-4310, McConnell, Steve C. (2004). Code Complete. Second Edition. Microsoft Press.
- #66 - Grammar in bad example of G-5030
- #67 - Wrong parameter in bad example of G-8410 (
in_lock_handle
instead ofin_lock_name
) - #68 - Typo in reason of G-8510