Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Trivadis PL/SQL & SQL Coding Guidelines v4.4

Latest
Compare
Choose a tag to compare
Loading
@PhilippSalvisberg PhilippSalvisberg released this 20 Mar 16:16
· 1 commit to main since this release

Version 4.4

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

Items marked with a 👮 require a change in the Linter tool suite db* CODECOP (besides including the changed guideline texts).

New

  • #210 Highlight the lines that violate a guideline in the bad examples (and the fixed lines in the good examples)
  • #212 New guideline G-3330: Avoid autonomous transactions. 👮
  • #213 New guideline G-4387: Never use a FOR LOOP for a query that should return not more than one row.

Changed

  • #208 Include column alias in the title of G-3182
    • old: G-3182: Always specify column names instead of positional references in GROUP BY clauses.
    • new: G-3182: Always specify column names/aliases instead of positional references in GROUP BY clauses.

Fixed

  • #205 Fix revision history in about page
Morty Proxy This is a proxified and sanitized view of the page, visit original site.