- Released on 2019-09-28
- Changed
- Guidelines
- Link to Trivadis PL/SQL & SQL Guidelines v3.6 in HTML report.
- Renamed G-3130 from “Try to use ANSI-join syntax” to “Try to use ANSI SQL-92 join syntax”.
- Renamed G-3160 from “Avoid virtual columns to be visible” to “Avoid visible virtual columns”.
- 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”.
- PL/SQL grammar
- Support keyword
MODand other keywords as query_name in the subquery_factoring_clause. - Support keyword
ONE, e.g. as column alias. - Support keyword
WELLFORMED, e.g. as parameter name. - Support keyword
WORK, e.g. as parameter name.
- Support keyword
- Included preview/trial license is valid thru 2020-03-31
- Guidelines
- Fixed
- Guidelines
- G-3120: false positive when using
SYSDATE,SYSTIMESTAMP,NULL,LEVEL,ROWNUM,CONNECT_BY_ISLEAFin query with joins.
- G-3120: false positive when using
- PL/SQL grammar
- Parse error when using udf_pragma.
- Parse error when using record with dot notation in values_clause of
INSERTstatement. For exampleINSERT INTO t VALUES in_param.rec. - Parse error when using
NOTin expressions withA SET,NAN,INFINITE,PRESENT,EMPTY,JSON,OF TYPE. Fore examplex IS NOT A SET.
- Guidelines
- Won’t Fix
- Support of keyword
JSONin table name or table alias due to conflicts with JSON_condition. - Empty conditional compilation branches (see also Parser Limitations)
- Support of keyword
Assets
3
- Released on 2019-04-04
- Fixed
- Guidelines
- G-3120 – false positive when using constants in projection.
- G-4140 – false positive when using
FORALLstatement. - G-7110 – false positive when using functions/procedures with a single parameter.
- PL/SQL grammar
- Parse error when using
PRAGMA INLINEwith a second string parameter.
- Parse error when using
- Guidelines
- Changed
- PL/SQL grammar
- Support keyword
EXCLUDE, e.g. as procedure name. - Support keyword
INSTANTIABLE, e.g. as column name. - Support quote literal character
/(see also Parser Limitations)
- Support keyword
- SQL*Plus grammar
- Support
$as alias forHOSTcommand.
- Support
- HTML report refers to the Trivadis PL/SQL & SQL Coding Guidelines Version 3.3 hosted on GitHub.
- PL/SQL grammar
Assets
2
- Released on 2017-09-22
- Fixed:
- Using quote delimiter character
~(tilde) leads to parse errors - Parse error when using
COUNTinpivot_clause
- Using quote delimiter character
Assets
2
- Released on 2017-08-15
- Fixed:
- Using concatenation operator
||with whitespace between the vertical bars leads to parse errors
- Using concatenation operator
- Changed
- Documented limitation regarding error_logging_clause, see Parser Limitations for examples
Assets
2
- Released on 2017-05-14
- New:
- Oracle 12.2.0.1 grammar support
- SQL*Plus
- History command
- SQL
- Analytic views
- Join groups
- Oracle sharding
- PDB lockdown profiles
ADMINISTER KEY MANAGEMENTEnhancementsFLASHBACK DATABASEEnhancementSELECTEnhancement- New
COLLATEOperator - New or Enhanced Expressions
- Enhanced Condition
- New or Enhanced Functions
- PL/SQL
ACCESSIBLE BYclause Enhancements- Data-Bound Collation
- PL/SQL Expressions Enhancements
- Support for SQL JSON operators in PL/SQL (based on SQL changes)
- PL/SQL Coverage Pragma
- PL/SQL Deprecation Pragma
- Sharing Metadata-Linked Application Common Objects
- SQL*Plus
- Oracle 12.2.0.1 grammar support
- Changed:
- Halstead based metrics may produce slightly higher values, since all data types are processed as operators
- Fixed:
- Parsing errors in
XMLELEMENTand other functions when using certain non-standard function parameters
- Parsing errors in
Assets
2
- Released on 2017-02-05
- New:
- Supporting Trivadis PL/SQL & SQL Coding Guidelines Version 3.2
- New guideline numbering scheme
- 13 new guidelines
- Check implemented:
- G-2230: Try to use SIMPLE_INTEGER datatype when appropriate.
- G-3150: Try to use identity columns for surrogate keys.
- G-3180: Always specify column names instead of positional references in ORDER BY clauses.
- G-3190: Avoid using NATURAL JOIN.
- G-7460: Try to define your packaged/standalone function to be deterministic if appropriate.
- G-7810: Do not use SQL inside PL/SQL to read sequence numbers (or SYSDATE)
- G-8120: Never check existence of a row to decide whether to create it or not.
- G-8310: Always validate input parameter size by assigning the parameter to a size limited variable in the declaration section of program unit.
- Check not yet implemented (requires
CREATE TABLEandALTER TABLEparser support, see ticket PLSQLCOP-212):- G-3160: Avoid virtual columns to be visible.
- G–3170: Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.
- Check not planned to be implemented (checks per source file are not suited for this kind of guidelines):
- G-5010: Try to use a error/logging framework for your application.
- G-8410: Always use application locks to ensure a program unit only running once at a given time.
- G-8420: Always use dbms_application_info to track program process transiently
- Check implemented:
- Guidelines categorised by Severity: Blocker (2), Critical (7), Major (46), Minor (37), Info (1)
- Guidelines assigned to one or more SQALE characteristics: Changeability (10), Efficiency (20), Maintainability (48), Portability (7), Reliability (34), Reusability (3), Security (1), Testability (11)
- Guidelines assigned to one of the 31 SQALE subcharacteristics supported by SonarQube.
- Defined effort to solve for every guidelines using a remediation functions supported by SonarQube.
- Severity and SQALE characteristics are included in HTML and Excel outputs, issues are ordered by severity (Blocker, Critical, Major, Minor, Info)
- Provided guideline example files include the new bad and good examples according Trivadis PL/SQL & SQL Coding Guidelines Version 3.2 and have been renamed to include the version 3 and version 2 guideline identifiers, e.g. guideline_2150_12.sql
- Extended valid values for
checkandskipcommand line options- Severities (blocker, critical, major, minor, info) may be used in
checkandskiplists - SQALE characteristics (changeability, efficiency, maintainability, portability, reliability, reusability, security, testability) may used in
checkandskiplist - Guideline numbers, severities and SQALE characteristics may be combined in
checkandskiplists
- Severities (blocker, critical, major, minor, info) may be used in
- Validators are plug-ins now, the following validators are included:
com.trivadis.tvdcc.validators.TrivadisGuidelines3– Trivadis PL/SQL & SQL Coding Guidelines Version 3.2 (default)com.trivadis.tvdcc.validators.TrivadisGuidelines2– Trivadis PL/SQL & SQL Coding Guidelines Version 2.0com.trivadis.oracle.plsql.validation.EmptyPLSQLJavaValidator– validator without checks, useful to produce code metrics only
- New preferences
validatorandplugin pathto configure provided and custom validators
- Supporting Trivadis PL/SQL & SQL Coding Guidelines Version 3.2
- Fixed:
- McCabe’s cyclomatic complexity metric increased wrongly by ELSE in IF/CASE branches, by PL/SQL blocks and by GOTO statements
- Guideline 3120 (27) does not detect correlated subqueries without alias
- Guideline 4340 (42) does not detect collection method COUNT in basic loop statements when used with empty parenthesis ()
- Guideline 4350 (43) and guideline 4360 (44) are not handled as mutually exclusive, but they are
- Guideline 4395 (50) false negatives when using “..” operator without leading space in for loops
- Guideline 5060 (56) false positives if more than one exception is defined in an exception handler
- Guideline 7110 (60) does not detect missing named notation when calling program units with a single parameter
- Guideline 7130 (62) false positives and false negatives in various cases
- single_table_insert with values_clause leads to parse errors in SQL scripts if terminated by slash instead of semicolon
- greater equal (>=) and less equal (<=) are reported as less than (<)
Assets
2
- Released on 2016-12-16
- Extended grammar to support additional keyword PERIOD, e.g. as variable name
- Extended grammar to support keywords as measure_column of a cell_assignment in the model_clause
Assets
2
- Released on 2016-09-05
- Fixed grammar to support inline views as target of a MERGE statement (undocumented)
- Fixed grammar to support
ASC|DESCandNULLSFIRST|LASTin row_pattern_order_by clause (undocumented)
Assets
2
- Released on 2016-08-26
- Guideline 04 (avoid dead code in your programs): fixed false positive when using subquery with false condition in
insert_into_clause - Guideline 56 (avoid unhandled exceptions): fixed false positives when using aggregation functions
AVG,MAXorMINin SELECT INTO Statement - Fixed grammar to support default namespace at any position within
XMLnamespaces_clause - Fixed grammar to support Temporal Validity in
flashback_query_clause - Fixed grammar to support
VARCHARwithBYTEandCHARsemantics (asVARCHAR2) - Extended grammar to support multiple
flashback_query_clause - Extended grammar to support
~as quote delimiter character - Extended grammar to support additional keywords, e.g. as variable name
- body
- show
- subtype
- versions
Assets
2
- Released on 2016-05-05
- Fixed parse errors when using database link in merge statement.
Assets
2
PreviousNext