Code Inspections in SQL
|Unresolved reference|| |
This inspection performs unresolved SQL references check.
|Types compatibility|| |
This inspection performs type-related check.
|Unused variable|| |
This inspection performs unused argument/variable check.
|Unused subquery item|| |
This inspection reports unused subquery items: columns and aliases that are not referenced in the outer query expression
|Identifier should be quoted|| |
This inspection performs SQL identifier names check.
|Ambiguous reference|| |
This inspection checks that column reference resolves to a single column.
|VALUES clause cardinality|| |
This inspection checks that the number of VALUES (...) parameters matches target table column list size.
|SQL dialect detection|| |
Detects the best matching SQL dialect for files in <Generic> dialect.
|Current console schema introspected|| |
Warns if current session's schema/database is not introspected.
|SQL source modification detection|| |
Detects that database sources have changed.
|No data sources configured|| |
Prompts one to create a data source if there is none.
|Each derived table should have alias|| |
This inspection checks that each derived table should have own alias.
|Column should be in group by clause|| |
This inspection checks that column should be in group by clause or inside aggregate function call.
|Constant condition|| |
Reports those conditions in the where or join clauses that are alwaystrue or false.
|Auto-increment duplicate|| |
This inspection checks auto_increment duplicates in MySQL, MS SQL and Db2 dialects. A table in those dialects can contain only one auto-incrementing field.
|Index is dependent on column|| |
This inspection checks dropping indexed columns in MS SQL and Sybase SQL Server.
|Adding not null column without default value|| |
Necessary to specify the default value for the new column with not null constraint.
|Check using clause columns|| |
This inspection checks that columns inside using clause exist in both tables.
|Null comparison|| |
This inspection checks suspicious comparisons with NULL.
|Function signature|| |
This inspection performs function signature check.
|Statement with side effects|| |
This inspection only runs during a read-only connection andreports statements that may lead to modification of the database.
|Delete or update statement without where clauses|| |
Reports usages of 'delete' or 'update' statements without any 'where' clauses.When used without 'where' clauses, 'delete' drops all the data from the table, and 'update' overwrites values for all table rows.
|SQL error handling|| |
Highlights invalid usages of constructs that handle exceptions in SQL routines
|Unsafe 'join' clause in 'delete' statement|| |
Reports usages of 'join' clause inside a 'delete' statement where no 'on' or 'where' checks are present.Without conditional checks on 'join', 'delete' drops contents of the entire table.
|Unreachable code|| |
This inspection reports unreachable statements inside SQL routines.
|Illegal cursor state|| |
This inspection reports illegal cursor states inside SQL routines.
|Named arguments should be used|| |
This inspection reports routine calls without named arguments
|Usages of GOTO statements|| |
This inspection reports usages of a GOTO statement
|Suspicious or incorrect usages of built-in functions|| |
This inspection reports suspicious or incorrect use cases of SQL Server built-in functions
|Suspicious code in triggers|| |
This inspection reports incorrect usages of transition table variables in triggers
|Redundant ordering direction|| |
This inspection reports redundant ordering direction in ORDER BY clauses.
|Aggregate-related problems|| |
This inspection reports incorrect or suspicious usages of SQL aggregate functions.
|Using CASE instead of conditional function and vice versa|| |
This inspection reports CASE expressions which can be replaced with IF-like function calls or vice versa depending on the chosen preferences
|Using CASE instead of COALESCE function and vice versa|| |
This inspection reports CASE expressions which can be replaced with COALESCE calls or vice versa depending on the chosen preferences
|Implicit string truncation|| |
Detects variable assignments which involve implicit string truncation
|Redundant alias expressions|| |
This inspection reports redundant alias expressions
|Redundant row limiting in queries|| |
This inspection reports redundant row limiting in queries.
|Multiple row limiting/offset clauses in queries|| |
This inspection reports queries with multiple row limiting/offset clauses.
|Insertion into generated columns|| |
This inspection reports INSERT statements which assign values to generated columns
|MySQL: Syntax|| |
Provides diagnostic of MySQL parser idiosyncrasies.
|Deprecated type|| |
Since 8.0 the 'long' type is deprecated and not recommended to use (because API for this type doesn't utilize character streams but transfer whole values each time). In Oracle, do not create a table with LONG columns. Use LOB columns (CLOB, NCLOB, BLOB) instead. LONG columns are supported only for backward compatibility.
|Postgres: Select from procedure call|| |
Select from dblink or function that returns record require typed alias list.Scalar functions do not require alias and forbid typed alias lists completely.