Suspicious code in triggers

Reports incorrect usages of transition table variables in triggers.

Example (HSQLDB):

CREATE TABLE foo(a INT);

CREATE TRIGGER trg
 AFTER DELETE ON foo
BEGIN
   SELECT * FROM NEW;
END;

CREATE TRIGGER trig AFTER INSERT ON foo
   REFERENCING OLD ROW AS newrow
   FOR EACH ROW WHEN (a > 1)
   INSERT INTO foo VALUES (1)

In HSQLDB, DELETE triggers may be used only with the OLD state while INSERT triggers may have only the NEW state. So, in the previous example, NEW in SELECT * FROM NEW; will be highlighted as well as OLD in REFERENCING OLD ROW AS newrow.

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.

SqlTriggerTransitionInspection

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

Availability

By default bundled with: CLion 2024.1, DataGrip 2024.1, DataSpell 2024.1, GoLand 2024.1, IntelliJ IDEA 2024.1, JetBrains Rider 2023.3, PhpStorm 2024.1, PyCharm 2024.1, Qodana for .NET 2023.3, Qodana for Go 2024.1, Qodana for JVM 2024.1, Qodana for PHP 2024.1, Qodana for Ruby 2024.1, RubyMine 2024.1,
Can be installed with plugin: Database Tools and SQL, 241.SNAPSHOT

Last modified: 18 June 2024