PL/SQL Cop for SQL Developer v2.3.0

• 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 MOD and 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.
  • Included preview/trial license is valid thru 2020-03-31
• Fixed
  • Guidelines
    • G-3120: false positive when using SYSDATE, SYSTIMESTAMP, NULL, LEVEL, ROWNUM, CONNECT_BY_ISLEAF in query with joins.
  • PL/SQL grammar
    • Parse error when using udf_pragma.
    • Parse error when using record with dot notation in values_clause of INSERT statement. For example INSERT INTO t VALUES in_param.rec.
    • Parse error when using NOT in expressions with A SET, NAN, INFINITE, PRESENT, EMPTY, JSON, OF TYPE. Fore example x IS NOT A SET.
• Won’t Fix
  • Support of keyword JSON in table name or table alias due to conflicts with JSON_condition.
  • Empty conditional compilation branches (see also Parser Limitations)