Renamed a column and the app broke: "column does not exist"

VERICTO-016 High In CI (offline CLI): FLAGGED

After ALTER TABLE users RENAME COLUMN name TO full_name; every query that still says name fails with ERROR: column "name" does not exist. No data was lost: a rename only changes the catalog. The fastest way out is to rename it back (ALTER TABLE users RENAME COLUMN full_name TO name;) and redo the change in steps that running code can survive.

Why it happens

The database changes instantly, but the code that uses it does not: the old application version is still running during a deploy, other services, reports and ORM caches still use the old name, and a rollback of the application brings back code that expects name. Renaming a table has the same effect on every query that names it.

How to fix it

Use expand/contract instead of a rename: add the new column, write to both, backfill, move the reads, and drop the old column only when nothing uses it.

ALTER TABLE users ADD COLUMN full_name text;
UPDATE users SET full_name = name WHERE full_name IS NULL;
-- deploy code that reads full_name, then later:
-- ALTER TABLE users DROP COLUMN name;

On a large table, run the backfill in batches.

How to stop it from happening again

VERICTO-016 · ALTER TABLE RENAME (table or column) · Severity: High · AST node: AlterTableStmt > Rename

The statement the rule reports

-- migrations/0046_rename_name.sql
ALTER TABLE users RENAME COLUMN name TO full_name;

Real CLI output

$ npx @vericto/vericto-cli@2.3.0 check --offline migrations/0046_rename_name.sql
note: offline mode: 42 standard rules at default severities, engine 5.1.0. Custom rules, overrides, sensitive columns, allowlists and the audit trail apply online only.
! migrations/0046_rename_name.sql  FLAGGED  VERICTO-016 high
    AlterTableStmt > Rename
    fix: Use a versioned migration tool and update all code references first
0 blocked · 0 allowed · 1 flagged · 0 monitored   (ruleset standard@engine-5.1.0 · mode: offline (engine 5.1.0, 42 standard rules, no workspace policy))

In a migration file the CLI marks it FLAGGED and exits with 0: a schema change in a migration is usually intended, so it is raised for review instead of blocked. With --fail-on flag (or fail_on = "flag" in .vericto.toml) it exits with 1 and the job fails. Outside a migration (--sql, stdin or another file) it blocks, as the proxy and MCP check_sql do.

The corrected version

-- migrations/0046_rename_name.sql
ALTER TABLE users ADD COLUMN full_name text;
$ npx @vericto/vericto-cli@2.3.0 check --offline migrations/0046_rename_name.sql
note: offline mode: 42 standard rules at default severities, engine 5.1.0. Custom rules, overrides, sensitive columns, allowlists and the audit trail apply online only.
0 blocked · 1 allowed · 0 flagged · 0 monitored   (ruleset standard@engine-5.1.0 · mode: offline (engine 5.1.0, 42 standard rules, no workspace policy))

Try it free, no account

The CLI checks your .sql files on your machine with the 42 standard rules: no sign-up, no API key, and no SQL leaves your computer. It is open source (AGPL-3.0-only).

npx @vericto/vericto-cli@2.3.0 check --offline migrations/

On every pull request

The vericto/check-sql GitHub Action (Apache-2.0) runs the same offline check on the .sql files a PR changes and annotates the findings on the PR. Save it as .github/workflows/vericto.yml:

on: pull_request
jobs:
  vericto:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
        with: { fetch-depth: 0 }
      - uses: vericto/check-sql@v1
        with: { offline: true, upload-sarif: false }

At runtime, for AI agents

The SQL an AI agent writes never goes through a PR. The Vericto TCP proxy checks each statement between the application or agent and the database, and the MCP check_sql tool lets the agent check SQL before it runs it. Both use the runtime profile, which also blocks schema changes.

The AST condition in the engine

The rule is a deterministic predicate over the AST, in src/rules/evaluator.rs of the open source engine (AGPL-3.0-only), at this page's commit:

"VERICTO-016" => find(stmts, |s| {
    s.kind == StatementKind::AlterTable
        && matches!(s.alter_table_kind, Some(AlterTableKind::Rename))
})
.map(|s| {
    let mut v = violation(
        rule,
        s,
        Some("Use a versioned migration tool and update all code references first".to_string()),
    );
    v.ast_node_path = "AlterTableStmt > Rename".to_string();
    v
}),

Frequently asked questions