docs/reference/rules/prefer-robust-stmts.md
Diagnostic Category: lint/safety/preferRobustStmts
Since: vnext
Sources:
Prefer statements with guards for robustness in migrations.
When running migrations outside of transactions (e.g., CREATE INDEX CONCURRENTLY), statements should be made robust by using guards like IF NOT EXISTS or IF EXISTS. This allows migrations to be safely re-run if they fail partway through.
CREATE INDEX CONCURRENTLY users_email_idx ON users (email);
code-block.sql:1:1 lint/safety/preferRobustStmts ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
! Concurrent index creation should use IF NOT EXISTS.
> 1 │ CREATE INDEX CONCURRENTLY users_email_idx ON users (email);
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2 │
i Add IF NOT EXISTS to make the migration re-runnable if it fails.
DROP INDEX CONCURRENTLY users_email_idx;
code-block.sql:1:1 lint/safety/preferRobustStmts ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
! Concurrent drop should use IF EXISTS.
> 1 │ DROP INDEX CONCURRENTLY users_email_idx;
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2 │
i Add IF EXISTS to make the migration re-runnable if it fails.
CREATE INDEX CONCURRENTLY IF NOT EXISTS users_email_idx ON users (email);
DROP INDEX CONCURRENTLY IF EXISTS users_email_idx;
{
"linter": {
"rules": {
"safety": {
"preferRobustStmts": "error"
}
}
}
}