Illegal cursor state

Reports illegal cursor states inside SQL routines.

A routine has CLOSE or FETCH statements but a cursor might be closed.
A routine has the OPEN statement but a cursor might be opened.

Example (Microsoft SQL Server):

CREATE TABLE t(col INT);

CREATE PROCEDURE foo() AS
BEGIN
DECLARE my_cursor CURSOR FOR SELECT * FROM t;
DECLARE a INT;
FETCH my_cursor INTO a;
CLOSE my_cursor;
END;

According to CLOSE (Transact-SQL) at docs.microsoft.com, CLOSE must be issued on an open cursor, and CLOSE is not allowed on cursors that have only been declared or are already closed. So, we need to open the cursor to fix the warning.

CREATE PROCEDURE foo() AS
BEGIN
DECLARE my_cursor CURSOR FOR SELECT * FROM t;
DECLARE a INT;
OPEN my_cursor;
FETCH my_cursor INTO a;
CLOSE my_cursor;
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.

SqlIllegalCursorState

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 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