Use of transaction management statements in triggers
Reports usages of transaction management statements like COMMIT or ROLLBACK in trigger bodies.
With COMMIT or ROLLBACK statements in a trigger body, the trigger will not compile. The fail happens because triggers start during transactions. When the trigger starts the current transaction is still not complete. As COMMIT terminates a transaction, both statements (COMMIT and ROLLBACK) would lead to an exception. Changes that are executed in a trigger should be committed (or rolled back) by the owning transaction that started the trigger.
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.
SqlTransactionStatementInTrigger- 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 Details | |
---|---|
By default bundled with: | CLion 2024.3, DataGrip 2024.3, GoLand 2024.3, IntelliJ IDEA 2024.3, JetBrains Rider 2024.3, PhpStorm 2024.3, PyCharm 2024.3, Qodana for .NET 2024.3, Qodana for Go 2024.3, Qodana for JS 2024.3, Qodana for JVM 2024.3, Qodana for PHP 2024.3, Qodana for Ruby 2024.3, RubyMine 2024.3, WebStorm 2024.3 |
Can be installed with plugin: | Database Tools and SQL, 243.23140 |