PL/SQL Cop for SQL Developer v3.0.1
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