Skip to content

Releases: Trivadis/plsql-cop-sqldev

db* CODECOP for SQL Developer v4.3.1

20 Jan 10:54
Compare
Choose a tag to compare

New

Compatibility with SQL Developer

  • Minimum version: 4.1.0
  • Latest version tested: 22.2.1

db* CODECOP for SQL Developer v4.3.0

02 Sep 20:13
Compare
Choose a tag to compare

New

  • Based on db* CODECOP v4.3.0

  • PLSQLCOP-435: By default, disable checks which cause a lot of false positives

    • Checks marked as "disabled" will be skipped, when the Guideline skip list preference is empty
    • To enable all checks configure none in the Guideline skip list preference

Compatibility with SQL Developer

  • Minimum version: 4.1.0
  • Latest version tested: 22.2.0

db* CODECOP for SQL Developer v4.2.2

14 Dec 17:44
Compare
Choose a tag to compare

New

Fixed

  • PLSQLCOP-405: Logging to system console, use logging framework instead (CWE 398)

    • This happend when opening a report in the default browser, but the default browser could not be detected.
  • PLSQLCOP-406: Printing stack trace to console, use logging framework instead (CWE 400, 200)

    • This happend in various error cases, where only the error message was logged.
    • Now the complete stack trace is also logged.

Compatibility with SQL Developer

  • Minimum version: 4.1.0
  • Latest version tested: 21.4.0

db* CODECOP for SQL Developer v4.2.1

28 Sep 12:31
Compare
Choose a tag to compare

New

Compatibility with SQL Developer

  • Minimum version: 4.1.0
  • Latest version tested: 21.2.1

db* CODECOP for SQL Developer v4.2.0

13 Sep 11:47
Compare
Choose a tag to compare

New

Fixed

  • PLSQLCOP-399: No code templates visible in preferences after running Check

Compatibility with SQL Developer

  • Minimum version: 4.1.0
  • Latest version tested: 21.2.1

db* CODECOP for SQL Developer v4.1.0

15 May 18:53
Compare
Choose a tag to compare

New

db* CODECOP for SQL Developer v4.0.4

03 Apr 01:34
c97d549
Compare
Choose a tag to compare

New

Changed

  • PLSQLCOP-312: Rebrand "PL/SQL Cop for SQL Developer" to "db* CODECOP for SQL Developer"

PL/SQL Cop for SQL Developer v3.0.1

21 Nov 11:23
Compare
Choose a tag to compare

New

  • Common

    • PLSQLCOP-271: JDK 8 is required, JDK 11 is supported
    • PLSQLCOP-275: Xtext and Xtend updated to v2.23.0 (important for custom validators)
    • Custom validators for PL/SQL Cop v2 are not supported (need to be updated to v3)
  • Validator (com.trivadis.tvdcc.validators.TrivadisGuidelines3)

    • PLSQLCOP-284: G-7410: do not throw warning for standalone functions with aggregate_clause
    • PLSQLCOP-285: G-8310: do not throw warning for "OUT" only parameter

Fixed

  • SQL*Plus Grammar

    • PLSQLCOP-274: Space slash NL not handled (for files with Unix line separators only)
  • PL/SQL Grammar

    • PLSQLCOP-262: Parse error when using a * (star) for precision in number data type
    • PLSQLCOP-276: Parser error when TABLE operator is not used for package function
    • PLSQLCOP-277: Parse error when using expressions without space in for loop
    • PLSQLCOP-280: Parse errors when update statements are terminated with slash instead of semicolon (Trivadis/plsql-cop-sonar#1)
    • PLSQLCOP-287: Parse error when using apex_escape.json due to JSON keyword
  • Validator (com.trivadis.tvdcc.validators.TrivadisGuidelines3)

    • PLSQLCOP-283: G-7110 false positives when initializing a collection with user prefix and new operator
    • PLSQLCOP-286: Parse error with when using a variable/constant for error_code in pragma exception_init
    • PLSQLCOP-288: False positive on G-8110 when using "ROWNUM = 1"
    • PLSQLCOP-289: G-6020: False positive with using_clause and in parameter mode

PL/SQL Cop for SQL Developer v2.3.2

30 Mar 08:19
Compare
Choose a tag to compare
  • Fixed
    • Serverity and characteristics are not honored in Issues tab. Default values are shown when using an own validator with a different guideline naming scheme (works in Reports tab).

PL/SQL Cop for SQL Developer v2.3.1

29 Mar 16:11
Compare
Choose a tag to compare
  • Fixed
    • Common

      • incomplete results when analyzed source code contains TREAT (due to NPE, see #1)
      • When using a own validator with a different guideline naming scheme the configured severity and characteristics per guideline are not honored and the defaults are reported (Blocker for severity and all characteristics)
    • Guidelines

      • G-7230 should not be thrown for constants in package specifications (see #79)
    • SQL*Plus grammar

      • Wrong line reported after comment lines ending on slash (/) for files using Unix line separators
    • PL/SQL grammar

      • Parse error when JSON_value_return_type is not defined.
        Documentation changed between version 12c and 18c. However, the following code works in Oracle Database 12c Release 1:

        SELECT *
          FROM JSON_TABLE (
                  (SELECT '{"col1":"foo"}' doc FROM dual), 
                  '$' COLUMNS (col1  PATH '$.col1')
               );
      • Parse error when a row_limiting_clause is used without an order_by_clause

      • Parse error when using expressions for offsetor rowcount in row_limiting_clause