drizzle-kit push compares your Drizzle schema with the database and applies the difference directly, with no SQL file. With --force it auto-accepts every data-loss statement in that difference, so the tables and columns it decides to drop go without a prompt. If it ran against production, the data is no longer in the database: restore from a point-in-time restore or a backup, to just before the push.
Recover now
- Stop the agent or the process. End the agent session, cancel any background task, and stop the test run, deploy job or service that ran the command, so nothing runs again against the database you are about to restore.
- Do not push again to recreate the tables: they come back empty. Write down when the push ran; every restore below needs that moment.
- Restore to a point just before the command, into a separate instance. Self-managed PostgreSQL: restore the base backup and replay the archived WAL with
recovery_target_timeset just before it; apg_dumpfile restores only to when it was taken. Amazon RDS / Aurora: "Restore to point in time" creates a new DB instance (RDS) or cluster (Aurora) at any moment within the backup retention period, without modifying the source. Neon: instant restore takes a root branch back to a moment within its history window. Supabase: the daily backups and, where it is enabled, point-in-time recovery are under Database → Backups. Railway: volume backups, if they were created or scheduled, are restored from the service. MySQL: restore the last full backup, then replay the binary log withmysqlbinlogup to just before the destructive event. - Check the restored copy, then move it back. Compare row counts and the latest rows with what you expect, then point the application at the restored instance or copy the tables back (
pg_dump -t tablefrom the restored instance). Rows written between the restore point and now must be re-applied by hand. - No backup and no point-in-time recovery? Look for other copies: a staging or development database, a read replica, exports, a data warehouse, or the systems the data came from.
Why it happened
Push is built to make the database match the schema, and a table or column the schema does not describe the way the database has it is part of the difference. Without --force, Drizzle stops and asks before the statements that lose data; with it, nobody is asked. In the public report (anthropics/claude-code#27063), an agent in a separate terminal ran drizzle-kit push --force against production PostgreSQL on Railway. The developer writes that --force was used to avoid being blocked by an interactive prompt, that the database had no automatic backups or point-in-time recovery, and that it was the second time drizzle-kit push had caused data loss in that project.
drizzle-kit push vs migrate, and the dry run
Per the Drizzle docs, drizzle-kit push reads your schema, introspects the database, generates SQL from the difference and applies it, with no SQL file. Its CLI-only options are --verbose (print all SQL statements before execution), --explain (print the planned SQL changes without applying them, a dry run) and --force (auto-accept all data-loss statements). Check npx drizzle-kit push --help for the options of your version.
drizzle-kit generate writes the difference as a migration.sql file instead, and drizzle-kit migrate applies the files not yet recorded in the __drizzle_migrations table. The docs present push as the fast path for prototyping and note teams also use it in production. If you do, look at the plan first (--explain or --verbose) and never pass --force against production. "Non-interactive" is what --force buys, and also what makes it dangerous: for an unattended run, generate and migrate give you a file someone reviewed.
How to prevent it
The statements drizzle-kit push applies are ordinary SQL on its connection. When it connects through the proxy, the DROP TABLE and ALTER TABLE … DROP COLUMN in the difference are blocked before they reach the database, with or without --force: the flag answers Drizzle's prompt, not the proxy.
Vericto checks each SQL statement on its AST before it reaches the database. These are the rules that report the statements of this incident, with the real CLI output on each rule's example:
VERICTO-010: DROP TABLE or DROP DATABASE
The rule's example · Critical
-- migrations/0042_drop_users.sql
DROP TABLE users;
Real CLI output
$ npx @vericto/vericto-cli@2.3.0 check --offline migrations/0042_drop_users.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/0042_drop_users.sql FLAGGED VERICTO-010 critical
DropStmt
fix: Use a versioned migration tool (Flyway, Prisma Migrate, Alembic, Rails migrations)
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.
VERICTO-015: ALTER TABLE DROP COLUMN
The rule's example · High
-- migrations/0045_drop_email.sql
ALTER TABLE users DROP COLUMN email;
Real CLI output
$ npx @vericto/vericto-cli@2.3.0 check --offline migrations/0045_drop_email.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/0045_drop_email.sql FLAGGED VERICTO-015 high
AlterTableStmt > AlterTableCmd.subtype = DROP_COLUMN
fix: Use soft-delete (nullable column) or a versioned migration tool
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.
Set up the agent so it goes through Vericto
- Connect the agent to the database through the proxy. Its connection URL points at the Vericto TCP proxy, not at the database. The proxy checks each statement, including the ones an ORM command run by the agent sends, and at runtime it blocks
DROP,TRUNCATEandALTER … DROP COLUMNbefore they reach the database. For a coding agent,vericto-proxy mcpgives itexecute_sql,describe_schemaandcheck_sql, never the database credential. - Keep the direct production credential away from the agent. Not in the
.env, the shell or the environment the agent and its test runs load. If the agent has another way to the database, the proxy does not see it. - Give it a read-only role through Vericto. The role behind
vericto-proxy mcpis read-only (the SQL to create it is in the MCP docs), and agent access sets each agent to read-only on the tables you choose. - Let the agent check SQL before it runs it with the MCP
check_sqltool: it gets the verdict, the rule and the suggested fix.
In CI, on the migration files
Move production to drizzle-kit generate plus drizzle-kit migrate: generate writes each change as a migration.sql file, and the Action checks it in the pull request, flagging a DROP for review before anyone applies it.
The vericto/check-sql GitHub Action (Apache-2.0) runs the same offline check on the .sql files a PR changes. 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 }
Or try the CLI on your machine, with no account (AGPL-3.0-only):
npx @vericto/vericto-cli@2.3.0 check --offline migrations/
Scope: Vericto protects the connections that go through Vericto. A shell on the database host, or a credential that connects directly, bypasses it.
Frequently asked questions
Sources
The public reports this page cites, checked on 2026-11-14, and the official docs behind each fact about the tools:
- anthropics/claude-code#27063 (February 20, 2026): a developer reports drizzle-kit push --force run against a production PostgreSQL database
- Drizzle docs: drizzle-kit push
- Drizzle docs: drizzle-kit generate
- Drizzle docs: drizzle-kit migrate
- PostgreSQL docs: continuous archiving and point-in-time recovery
- Amazon RDS docs: restoring a DB instance to a specified time
- Neon docs: instant restore (point-in-time restore of a root branch)
- Railway docs: volume backups
Related pages
- Claude Code deleted your production database or dropped a column? How to recover
- prisma migrate reset or db push --force-reset deleted your data? How to recover
- AI agent deleted your production database? What happened and how to recover
- VERICTO-010: DROP TABLE or DROP DATABASE
- VERICTO-015: ALTER TABLE DROP COLUMN
- When an AI agent runs destructive SQL on production