Database

void db push

Apply your Drizzle schema directly to the development database without creating migration files. D1 updates the local database; PostgreSQL and MySQL use DATABASE_URL from .env.

Use this for quick schema iteration while prototyping. Before deploying, generate and review migration files with void db generate.

void db generate

Generate SQL migration files from schema changes.

Compares your schema with the last Drizzle snapshot and writes migrations under db/migrations/. It includes Void-managed auth tables and configured auth plugins, even without an application schema. Review and commit the generated files before deploying.

For SQLite, Void checks that the migration history applies to a fresh database. If generation fails this check, the previous SQL, snapshots, and journal are restored. If an existing migration fails, repair that unapplied migration first: rerunning generation compares snapshots and does not repair existing SQL. This check does not verify that a migration preserves existing data; review table rebuilds and foreign-key actions carefully.

void db status

Show migration status. Displays which migrations are applied or pending locally, then uses the saved deployment target for remote status: the hosted API for Void projects, the pinned D1 database and its configured migration table for direct Cloudflare SQLite projects, or the shell DATABASE_URL for direct Cloudflare PostgreSQL/MySQL projects. If the remote credential or service is unavailable, local status is still shown.

void db reset

Drop the local D1 database and re-apply all migrations. Does not affect the remote database.

void db seed

void db seed [--file <path>]

Reset the local database, re-apply all migrations, then execute a seed file.

If --file is omitted, Void looks for default seed files in this order: db/seed.ts, db/seed.mts, db/seed.js, db/seed.mjs, db/seed.sql.

If more than one default seed file exists, the CLI stops and asks you to pass --file <path>.

Programmatic seed modules must export either a default function or a named seed function.

void db execute

void db execute <sql>
void db execute --file <path>
void db execute --remote <sql>

Run ad-hoc SQL against the database. Provide SQL inline or from a file. SELECT queries display results as a formatted table; other statements execute silently.

By default, targets the local database. Pass --remote to run against the deployed database selected in .void/project.json:

• Void platform D1 projects: routes the query through the selected platform's registered proxy using your auth token. Void Cloud's proxy is proxy.void.cloud; a self-hosted platform uses its own proxy URL.
• Direct Cloudflare D1 projects: invokes Cloudflare against the pinned D1 binding from void.config.ts or void.lock.json.
• Hosted PostgreSQL and MySQL projects: fetches the stored connection string from the platform and connects directly.
• Direct Cloudflare PostgreSQL and MySQL projects: uses DATABASE_URL from the current shell; Cloudflare cannot return the password from Hyperdrive.

For destructive statements (DELETE, UPDATE, DROP, etc.) when running in a TTY, you will be prompted to confirm before the query is sent to the deployed database. Non-TTY environments (CI) skip the prompt.

void db migrate

void db migrate [--remote]

Apply pending migrations to the local database without resetting. Unlike void db reset, this preserves existing data and only runs migrations that haven't been applied yet.

Pass --remote to apply pending migrations to the saved target. Hosted projects require a Void login and link. Direct Cloudflare D1 projects use the binding's configured migration directory, table, and pattern; direct PostgreSQL and MySQL projects use the shell DATABASE_URL.

void db studio

void db studio [--remote]

Open Drizzle Studio for the database. Launches a web-based GUI for browsing and editing your data.

By default, targets the local database. Pass --remote to open Studio against the deployed database:

• PostgreSQL and MySQL projects: fetch the stored connection string from the platform and open Studio against it. If the URL isn't stored yet, run void db set-url first.
• D1 projects: remote Studio is not yet supported. Use void db execute --remote for ad-hoc queries against your deployed D1 database.

On direct Cloudflare PostgreSQL/MySQL targets, remote Studio uses DATABASE_URL from the current shell. Direct D1 Studio remains unsupported; use void db execute --remote.

void db rename-migrations

Rename existing migrations from the old numeric prefix format (0001_name.sql) to timestamp-based format (20260410161500_name.sql). Updates local tracking table and remote records if logged in with a linked project.

void db connect

Connect an existing PostgreSQL/MySQL database or provision one through an adapter:

void db connect 'postgresql://user:password@host/database'
NEON_API_KEY=... void db connect --provider neon --name my-app
void db connect --provider @acme/void-db-provider --region region-id

The command saves DATABASE_URL in .env. When authenticated with a linked Void project, it also updates the encrypted deployment URL; pass --local-only to skip that sync. neon is built in. Other adapters are project dependencies or local modules exporting a DatabaseProviderAdapter from void/database-provider.

Provider-created credentials are never printed. For direct Cloudflare deploys, configure the same URL as a protected DATABASE_URL in the shell or CI environment that runs deploy.

void db set-url

Update the PostgreSQL or MySQL connection string for deployment. Available for projects with "database": "pg" or "database": "mysql".

Prompts for a connection string and sends it to the platform API to create or update the Hyperdrive configuration.

void db export

void db export [--output <path>] [--no-data] [--no-schema] [--table <name>]

Dump the local database as SQL. Outputs to stdout by default (pipeable), or to a file with --output.

Data exports preserve SQLite AUTOINCREMENT and PostgreSQL SERIAL and identity counters, including IDs consumed by deleted rows. SQLite schema exports include indexes, views, and triggers. PostgreSQL schema exports preserve column types, generated columns, identity definitions, serial sequences, constraints, and indexes. --no-schema restores counter values into an existing schema; --no-data starts counters at their schema-defined starting values.

For PostgreSQL schemas with views, triggers, custom types, functions, or standalone sequences, use pg_dump for a complete backup. void db export reports these objects before writing a schema dump.

Flag	Purpose
--output <path>	Write to a file instead of stdout
--no-data	Schema only (no INSERT statements)
--no-schema	Data only (no CREATE TABLE)
--table <name>	Export a single table