What are the limitations?

Maxim
If your SQL*Plus script runs successfully against an Oracle database but PL/SQL Cop or PL/SQL Analyzer reports an error, this is usually considered a bug. However, there are some known exceptions to this basic principle, which are documented below.

Block Terminator
Other block terminators than a dot (.) are not supported. This means the “SET BLOCKTERMINATOR” command is ignored.

Command Separator
Other command separators than semicolon (;) are not supported. This means that the “SET CMDSEP” command is ignored.

SQL Terminator
Other SQL terminators than semicolon (;) are not supported. This means that the “SET SQLTERMINATOR” command is ignored. Tailing whitespaces after a SQL terminator are not supported.

Line Continuation Character
Tailing whitespaces after a line continuation character (-) are not supported.

Slash Command
Tailing whitespaces after the slash command (/) are not supported.

Execute Command
The execute command must end on semicolon (;) if the last token is an expression.

Remark Command
The remark must not contain unterminated single or double quotes.

Prompt Command
The prompt must not contain unterminated single or double quotes.

Use of Keywords
The use of PL/SQL and SQL keywords as unquoted identifiers are generally not supported, due to the fact, that every single keyword needs to be treated as an exception. Oracle is quite gracious in that area and therefore we are eager to support more and more keywords as unquoted identifiers with every release, but the following keywords are causing conflicts in certain parts of the grammar and the use as literals should be therefore avoided: CROSS, CURSOR, END, FULL, FUNCTION, INNER, JOIN, LEFT, MODEL, OUTER, RIGHT, ROWTYPE, TYPE.

Quote Delimiter Characters
Oracle supports various quote literal characters except space, tab and return. The following example uses the [] quote character pair:

The following quote characters-pairs are supported: $$, ##, @@, ££, ||, (), {}, [], <>, !!, ++, ~~. All other quote characters lead to parse errors.

Conditional Compilation

Up until PL/SQL Cop version 1.0.16, PL/SQL Cop for SQL Developer 1.0.12, PL/SQL Analyzer 1.0.7 conditional compilation blocks have been fully analysed in the PL/SQL body, but were not supported in the PL/SQL DECLARE section.

Since it is possible to store non-PL/SQL code within conditional compilation blocks, e.g. generation templates as used in FTLDB or tePSQL, the full-fletched analysis support of directive IF statements has been dropped. The “$IF … $END” and the “$ERROR … $END” code blocks are still recognised as statements/expressions including conditions, but the rest of the code is just parsed as a series of tokens. As a side effect, metrics such as the number of statements might change.

The current PL/SQL parser supports conditional compilation within the DECLARE section as ITEM_LIST_1 or ITEM_LIST_2.

Error Logging Clause
The keyword “log” is supported as table name and table alias. As a side effect DELETE and INSERT statements with an error_logging_clause but without a where_clause and without table alias cannot be supported.

PL/SQL Source Text Wrapping
Since PL/SQL Cop and PL/SQL Analyzer do not include a PL/SQL unwrap utility, the use of wrapped PL/SQL code is not supported.

Supported Oracle Versions
The PL/SQL and SQL grammars from Oracle version 7.0 until version 12.2 are supported. The language is based on the following documentation:

  • Oracle SQL*Plus User’s Guide and Reference, 12c Release 2 (12.2), E50028-08, January 2017
  • Oracle SQL Language Reference, 12c Release 2 (12.2), E49448-12, January 2017
  • Oracle PL/SQL Language Reference, 12c Release 2 (12.2), E49633-15, January 2017

Grammar extensions made in newer versions are not yet covered.