Inspectopedia 2025.2 Help

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; <<a>> x := 1; IF (n = 0) THEN GOTO a; END IF; WHILE TRUE LOOP GOTO b; END LOOP; <<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 ID: SqlGotoInspection

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

Option ID:

mode

Default value:

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

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection SqlGoto

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

Last modified: 18 September 2025