Usages of GOTO statements

Reports usages of backward GOTO statements and GOTO statements used to exit a loop.

The extensive use of GOTO statements is generally not recommended. For details, see GOTO statement in SQL procedures at ibm.com.

Instead of jumping back to a previous statement using GOTO, consider using a loop.

Instead of exiting the WHILE loop with GOTO, consider using other control-of-flow statements (for example, RETURN or BREAK).

Example (Oracle):

CREATE PROCEDURE test(n INT) AS
DECLARE
    x INT;
BEGIN
    x := 0;
    GOTO a;
    &lt;&lt;a>> x := 1;
    IF (n = 0) THEN
        GOTO a;
    END IF;
    WHILE TRUE
        LOOP
            GOTO b;
        END LOOP;
    &lt;&lt;b>> x := 3;
END;

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

SqlGoto

Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | SQL

Inspection options

Here you can find the description of settings available for the Usages of GOTO statements inspection, and the reference of their default values.

Report

Default setting: Backward GOTO and uses of GOTO to exit a loop

Other available settings:

Uses of GOTO statements to exit a loop
Backward GOTO statements
All GOTO statements

Inspection Details
By default bundled with:	CLion 2024.2, DataGrip 2024.2, GoLand 2024.2, IntelliJ IDEA 2024.2, JetBrains Rider 2024.2, PhpStorm 2024.2, PyCharm 2024.2, Qodana for .NET 2024.2, Qodana for Go 2024.2, Qodana for JVM 2024.2, Qodana for PHP 2024.2, Qodana for Ruby 2024.2, RubyMine 2024.2,
Can be installed with plugin:	Database Tools and SQL, 242.22903

Last modified: 11 September 2024