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):
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.
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:
modeDefault value:
Backward GOTO and uses of GOTO to exit a loopOther 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:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: | CLion 2026.1, DataGrip 2026.1, DataSpell 2026.1, GoLand 2026.1, IntelliJ IDEA 2026.1, JetBrains Rider 2025.3, PhpStorm 2026.1, PyCharm 2026.1, Qodana for .NET 2025.3, Qodana for Go 2026.1, Qodana for JS 2026.1, Qodana for JVM 2026.1, Qodana for PHP 2026.1, Qodana for Ruby 2026.1, RubyMine 2026.1, WebStorm 2026.1 |