PL/SQL Cop for SQL Developer v1.0.18

• 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

PL/SQL Cop for SQL Developer v1.0.16

• Released on 2016-09-05
• Fixed grammar to support inline views as target of a MERGE statement (undocumented)
• Fixed grammar to support ASC|DESC and NULLS FIRST|LAST in row_pattern_order_by clause (undocumented)

PL/SQL Cop for SQL Developer v1.0.15

• 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, MAX or MIN in 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 VARCHAR with BYTE and CHAR semantics (as VARCHAR2)
• 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

PL/SQL Cop for SQL Developer v1.0.14

• Released on 2016-05-05
• Fixed parse errors when using database link in merge statement.

PL/SQL Cop for SQL Developer v1.0.13

• Released on 2016-04-26
• Fixed parse errors when conditional compilation blocks contain non PL/SQL code.

PL/SQL Cop for SQL Developer v1.0.12

• Released on 2015-11-23

• Guideline 16 (Avoid using overly short names for declared or implicitly declared identifiers) does not report variables used as index in basic loops, while loops and for loops. Variable names i and j are not ignored anymore.

• Reduced false negatives for guideline 24 (Try to use boolean data type for values with dual meaning). See also Validator Limitations.

• Extending grammar to support the IS OF type Condition fully
  

• Extending grammar to support additional keyword WITHIN e.g. as variable name

PL/SQL Cop for SQL Developer v1.0.11

• Released on 2015-09-07
• Fixed broken link to Trivadis PL/SQL & SQL Coding Guidelines Version 2.0
• Fixed “number of statements (PL/SQL)” metric. Labels are not counted as statements anymore.
• Fixed calculation of Halstead volume, leading to lower values
  • Percent operators are not counted as slash operators
  • Procedure call operators are not counted additionally as function call operators
  • Strings operands are not counted twice

PL/SQL Cop for SQL Developer v1.0.10

• Released on 2015-04-11
• Fixed wrong column number in “Issues” tab
• Fixed error when analyzing code containing CDATA end tags ]]>

PL/SQL Cop for SQL Developer v1.0.8

• Released on 2015-04-06
• Oracle 12.1.0.2 grammar support (SQL*Plus, SQL and PL/SQL), e.g.
  • JSON
    • IS JSON condition
    • JSON_EXISTS condition
    • JSON_TEXTCONTAINS condition
    • JSON_QUERY
    • JSON_TABLE
    • JSON_VALUE
  • ZONE MAPS
    • CREATE MATERIALIZED ZONEMAP
    • ALTER MATERIALIZED ZONEMAP
    • DROP MATERIALIZED ZONEMAP
• Rating system for complexity metrics
  • Green, amber, red for
    • McCabe’s cyclomatic complexity
    • Halstead volume
    • Maintainability index
  • Legend explaining the rating system
• Additional metrics
  • lines of comments
  • blank lines
  • net lines of code (lines of code without blank lines and comment lines)
• Grammar fixes (supporting additional keywords such ass RULES, INTERFACE)
• Suppress warnings if errors are reported
• Changed context of guideline 60 (Try to use named notation when calling program units)
• Fixed false positives on guideline 42 (Always use a NUMERIC FOR loop to process a dense array)
• Fixed false positives on guideline 03 (Avoid defining variables that are not used) for variables or constants used in cursors only
• Fixed false positives on guideline 62 (Always use parameters or pull in definitions rather than referencing external variables) when sequence pseudocolumns CURRVAL and NEXTVAL are used
• Fixed non-working NOSONAR marker with a preceding comment
• Fixed wrong line number if analyzed statement starts with one or more new lines

PL/SQL Cop for SQL Developer v1.0.4

• Released on 2014-10-07
• Renamed “Trivadis PL/SQL & SQL CodeChecker for SQL Developer” to “Trivadis PL/SQL Cop for SQL Developer”