Skip to content

@PhilippSalvisberg PhilippSalvisberg released this Sep 28, 2019 · 5 commits to master since this release

Version 3.6

https://trivadis.github.io/plsql-and-sql-coding-guidelines/v3.6/
PLSQL-and-SQL-Coding-Guidelines.pdf

Fixed

  • #74 - Dead links in introduction chapter
  • #76 - Changed title of Urban Lankes in foreword
Assets 2

@PhilippSalvisberg PhilippSalvisberg released this Sep 21, 2019 · 9 commits to master since this release

Version 3.5

https://trivadis.github.io/plsql-and-sql-coding-guidelines/v3.5/
PLSQL-and-SQL-Coding-Guidelines.pdf

Improved

  • #13 - PLSQL-and-SQL-Coding-Guidelines.pdf included in HTML site in chapter Appendix
  • #73 - Static text in revision history with link to release information
Assets 2

@PhilippSalvisberg PhilippSalvisberg released this Sep 20, 2019 · 21 commits to master since this release

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 of in_lock_name)
  • #68 - Typo in reason of G-8510
Assets 2

@PhilippSalvisberg PhilippSalvisberg released this Jul 7, 2018 · 75 commits to master since this release

Version 3.3

https://trivadis.github.io/plsql-and-sql-coding-guidelines/v3.3/
PLSQL-and-SQL-Coding-Guidelines.pdf

Improved

  • #1 Split single word document into several markup files
  • #6 Ensure that every rule in chapter 4 (Language usage) has a reason
Assets 2

@PhilippSalvisberg PhilippSalvisberg released this Jun 13, 2018 · 133 commits to master since this release

Version 3.2

PLSQL-and-SQL-Coding-Guidelines.pdf

  • Released in January 2017
  • Various small corrections
Assets 2

@PhilippSalvisberg PhilippSalvisberg released this Jun 13, 2018 · 134 commits to master since this release

Version 3.1

PLSQL-and-SQL-Coding-Guidelines.pdf

  • Released in April 2016
  • Some corrections
Assets 2

@PhilippSalvisberg PhilippSalvisberg released this Jun 13, 2018 · 135 commits to master since this release

Version 3.0

PLSQL-and-SQL-Coding-Guidelines.pdf

  • Release in January 2016
  • Added rules for Oracle Database 12c
  • Added SQALE metrics
  • New guideline numbering system
Assets 2

@PhilippSalvisberg PhilippSalvisberg released this Jun 13, 2018 · 136 commits to master since this release

Version 2.0

PLSQL-and-SQL-Coding-Guidelines.pdf

  • Released in August 2011
  • Added error handling section
  • Added rule 23: Always define your VARCHAR2 variables using CHAR SEMANTIC
  • Added rule 30: Use BULK OPERATIONS (BULK COLLECT, FORALL) whenever you have to
    repeatedly execute a DML or SELECT command for more than 4 times.
  • Added rule 31: Always use %NOTFOUND instead of NOT %FOUND to check whether a cursor was
    successful.
  • Added rule 43: Use 1 as lower boundary and COUNT() as upper boundary when looping over a
    dense array.
Assets 2

@PhilippSalvisberg PhilippSalvisberg released this Jun 13, 2018 · 137 commits to master since this release

Version 1.3.1

PLSQL-and-SQL-Coding-Guidelines.pdf

  • Released in October 2010
  • Changed some formatting
Assets 2

@PhilippSalvisberg PhilippSalvisberg released this Jun 13, 2018 · 138 commits to master since this release

Version 1.3

PLSQL-and-SQL-Coding-Guidelines.pdf

  • Released in April 2010
  • Several Corrections
  • Added rule 72: Always prefix ORACLE supplied packages with owner schema name
Assets 2
You can’t perform that action at this time.