**Status**: Production Ready ✅ **Last Updated**: 2026-02-03 Command Purpose
/db-init/migrate/seed# 1. Install npm install drizzle-orm npm install -D drizzle-kit # 2. Configure drizzle.config.ts import { defineConfig } from 'drizzle-kit'; export default defineConfig({ schema: './src/db/schema.ts', out: './migrations', dialect: 'sqlite', driver: 'd1-http', dbCredentials: { accountId: process.env.CLOUDFLARE_ACCOUNT_ID!, databaseId: process.env.CLOUDFLARE_DATABASE_ID!, token: process.env.CLOUDFLARE_D1_TOKEN!, }, }); # 3. Configure wrangler.jsonc { "d1_databases": [{ "binding": "DB", "database_name": "my-database", "database_id": "your-database-id", "migrations_dir": "./migrations" // CRITICAL: Points to Drizzle migrations }] } # 4. Define schema (src/db/schema.ts) import { sqliteTable, text, integer } from 'drizzle-orm/sqlite-core'; export const users = sqliteTable('users', { id: integer('id').primaryKey({ autoIncrement: true }), email: text('email').notNull().unique(), createdAt: integer('created_at', { mode: 'timestamp' }).$defaultFn(() => new Date()), }); # 5. Generate & apply migrations npx drizzle-kit generate npx wrangler d1 migrations apply my-database --local # Test first npx wrangler d1 migrations apply my-database --remote # Then production # 6. Query in Worker import { drizzle } from 'drizzle-orm/d1'; import { users } from './db/schema'; const db = drizzle(env.DB); const allUsers = await db.select().from(users).all();
db.batch() for transactions - D1 doesn't support SQL BEGIN/COMMIT (see Issue #1) ✅ Test migrations locally first - Always --local before --remote ✅ Use integer with mode: 'timestamp' for dates - D1 has no native date type ✅ Use .$defaultFn() for dynamic defaults - Not .default() for functions ✅ Set migrations_dir in wrangler.jsonc - Points to ./migrationsBEGIN TRANSACTION - D1 requires batch API ❌ Never use drizzle-kit push for production - Use generate + apply ❌ Never mix wrangler.toml and wrangler.jsonc - Use wrangler.jsonc onlynpx drizzle-kit studio # Opens http://local.drizzle.studio # For remote D1 database npx drizzle-kit studio --port 3001
drizzle-kit generatedrizzle-kit pushdrizzle-kit pulldrizzle-kit checkdrizzle-kit up# Introspect existing D1 database npx drizzle-kit pull # Validate migrations haven't collided npx drizzle-kit check
.$dynamic():import { eq, and, or, like, sql } from 'drizzle-orm'; // Base query function getUsers(filters: { name?: string; email?: string; active?: boolean }) { let query = db.select().from(users).$dynamic(); if (filters.name) { query = query.where(like(users.name, `%${filters.name}%`)); } if (filters.email) { query = query.where(eq(users.email, filters.email)); } if (filters.active !== undefined) { query = query.where(eq(users.active, filters.active)); } return query; } // Usage const results = await getUsers({ name: 'John', active: true }); `### Upsert (Insert or Update on Conflict)` import { users } from './schema'; // Insert or ignore if exists await db.insert(users) .values({ id: 1, email: 'test@example.com', name: 'Test' }) .onConflictDoNothing(); // Insert or update specific fields on conflict await db.insert(users) .values({ id: 1, email: 'test@example.com', name: 'Test' }) .onConflictDoUpdate({ target: users.email, // Conflict on unique email set: { name: sql`excluded.name`, // Use value from INSERT updatedAt: new Date(), }, });
import { drizzle } from 'drizzle-orm/d1'; // Enable query logging const db = drizzle(env.DB, { logger: true }); // Custom logger const db = drizzle(env.DB, { logger: { logQuery(query, params) { console.log('SQL:', query); console.log('Params:', params); }, }, }); // Get SQL without executing (for debugging) const query = db.select().from(users).where(eq(users.id, 1)); const sql = query.toSQL(); console.log(sql.sql, sql.params);
D1_ERROR: Cannot use BEGIN TRANSACTION Source: https://github.com/drizzle-team/drizzle-orm/issues/4212 Why: Drizzle uses SQL BEGIN TRANSACTION, but D1 requires batch API instead. Prevention: Use db.batch([...]) instead of db.transaction()FOREIGN KEY constraint failed: SQLITE_CONSTRAINT Source: https://github.com/drizzle-team/drizzle-orm/issues/4089 Why: Drizzle uses PRAGMA foreign_keys = OFF; which causes migration failures. Prevention: Define foreign keys with cascading: .references(() => users.id, { onDelete: 'cascade' })Error: No such module "wrangler" Source: https://github.com/drizzle-team/drizzle-orm/issues/4257 Why: Importing from wrangler package in runtime code fails in production. Prevention: Use import { drizzle } from 'drizzle-orm/d1', never import from wranglerTypeError: Cannot read property 'prepare' of undefined Why: Binding name in code doesn't match wrangler.jsonc configuration. Prevention: Ensure "binding": "DB" in wrangler.jsonc matches env.DB in codeMigration failed to apply: near "...": syntax error Why: Syntax errors or applying migrations out of order. Prevention: Test locally first (--local), review generated SQL, regenerate if neededType instantiation is excessively deep and possibly infinite Why: Complex circular references in relations. Prevention: Use explicit types with InferSelectModel<typeof users>.all() or .get() methods, don't reuse statements across requestsstrict: true Why: Drizzle types can be loose. Prevention: Use explicit return types: Promise<User | undefined>Cannot find drizzle.config.ts Why: Wrong file location or name. Prevention: File must be drizzle.config.ts in project root--local for dev, --remote for productionwrangler.jsonc consistently (supports comments)too many SQL variables at offset Source: drizzle-orm#2479, Cloudflare D1 Limits Why It Happens: Cloudflare D1 has a hard limit of 100 bound parameters per query. When inserting multiple rows, Drizzle doesn't automatically chunk. If (rows × columns) > 100, the query fails. Prevention: Use manual chunking or autochunk pattern// 35 rows × 3 columns = 105 parameters → FAILS const books = Array(35).fill({}).map((_, i) => ({ id: i.toString(), title: "Book", author: "Author", })); await db.insert(schema.books).values(books); // Error: too many SQL variables at offset `**Solution - Manual Chunking**:` async function batchInsert<T>( db: any, table: any, items: T[], chunkSize = 32 ) { for (let i = 0; i < items.length; i += chunkSize) { await db.insert(table).values(items.slice(i, i + chunkSize)); } } await batchInsert(db, schema.books, books); `**Solution - Auto-Chunk by Column Count**:` const D1_MAX_PARAMETERS = 100; async function autochunk<T extends Record<string, unknown>, U>( { items, otherParametersCount = 0 }: { items: T[]; otherParametersCount?: number; }, cb: (chunk: T[]) => Promise<U>, ) { const chunks: T[][] = []; let chunk: T[] = []; let chunkParameters = 0; for (const item of items) { const itemParameters = Object.keys(item).length; if (chunkParameters + itemParameters + otherParametersCount > D1_MAX_PARAMETERS) { chunks.push(chunk); chunkParameters = itemParameters; chunk = [item]; continue; } chunk.push(item); chunkParameters += itemParameters; } if (chunk.length) chunks.push(chunk); const results: U[] = []; for (const c of chunks) { results.push(await cb(c)); } return results.flat(); } // Usage const inserted = await autochunk( { items: books }, (chunk) => db.insert(schema.books).values(chunk).returning() );
drizzle-seed. Use seed(db, schema, { count: 10 }) to limit seed size.findFirst with Batch API Returns Error Instead of UndefinedTypeError: Cannot read properties of undefined (reading '0') Source: drizzle-orm#2721 Why It Happens: When using findFirst in a batch operation with D1, if no results are found, Drizzle throws a TypeError instead of returning null or undefined. This breaks error handling patterns that expect falsy return values. Prevention: Use pnpm patch to fix the D1 session handler, or avoid findFirst in batch operations// Works fine - returns null/undefined when not found const result = await db.query.table.findFirst({ where: eq(schema.table.key, 'not-existing'), }); // Throws TypeError instead of returning undefined const [result] = await db.batch([ db.query.table.findFirst({ where: eq(schema.table.key, 'not-existing'), }), ]); // Error: TypeError: Cannot read properties of undefined (reading '0') `**Solution - Patch drizzle-orm**:` # Create patch with pnpm pnpm patch drizzle-orm `Then edit `node_modules/drizzle-orm/d1/session.js`:` // In mapGetResult method, add null check: if (!result) { return undefined; } if (this.customResultMapper) { return this.customResultMapper([result]); } `**Workaround - Avoid findFirst in Batch**:` // Instead of batch with findFirst, use separate queries const result = await db.query.table.findFirst({ where: eq(schema.table.key, key), });
-- D1 supports this, but Drizzle has no JS equivalent CREATE TABLE products ( id INTEGER PRIMARY KEY, data TEXT, price REAL GENERATED ALWAYS AS (json_extract(data, '$.price')) STORED ); CREATE INDEX idx_price ON products(price); `**Workaround - Use Raw SQL**:` import { sql } from 'drizzle-orm'; // Current workaround - raw SQL only await db.run(sql` CREATE TABLE products ( id INTEGER PRIMARY KEY, data TEXT, price REAL GENERATED ALWAYS AS (json_extract(data, '$.price')) STORED ) `); // Or in migration file (migrations/XXXX_add_generated.sql) CREATE INDEX idx_price ON products(price);
PRAGMA foreign_keys=OFF before table recreation, but Cloudflare D1 ignores this pragma. CASCADE DELETE still triggers, destroying all related data. Prevention: Manually rewrite dangerous migrations with backup/restore patternonDelete: "cascade", ALL related data is deleted.// Schema with cascade relationships export const account = sqliteTable("account", { accountId: integer("account_id").primaryKey(), name: text("name"), }); export const property = sqliteTable("property", { propertyId: integer("property_id").primaryKey(), accountId: integer("account_id").references(() => account.accountId, { onDelete: "cascade" // ⚠️ CASCADE DELETE }), }); // Change account schema (e.g., add a column) // npx drizzle-kit generate creates: // DROP TABLE account; -- ⚠️ Silently destroys ALL properties via cascade! // CREATE TABLE account (...); `**Safe Migration Pattern**:` -- Manually rewrite migration to backup related data PRAGMA foreign_keys=OFF; -- D1 ignores this, but include anyway -- 1. Backup related tables CREATE TABLE backup_property AS SELECT * FROM property; -- 2. Drop and recreate parent table DROP TABLE account; CREATE TABLE account ( account_id INTEGER PRIMARY KEY, name TEXT, -- new columns here ); -- 3. Restore related data INSERT INTO property SELECT * FROM backup_property; DROP TABLE backup_property; PRAGMA foreign_keys=ON;
DROP TABLE statements for tables with foreign key referencesonDelete: "cascade" relationshipsonDelete: "set null" instead of "cascade" for schema changessql Template in D1 Batch Causes TypeErrorTypeError: Cannot read properties of undefined (reading 'bind') Source: drizzle-orm#2277 Why It Happens: Using sql template literals inside db.batch() causes TypeError. The same SQL works fine outside of batch operations. Prevention: Use query builder instead of sql template in batch operationsconst upsertSql = sql`insert into ${schema.subscriptions} (id, status) values (${id}, ${status}) on conflict (id) do update set status = ${status} returning *`; // Works fine const [subscription] = await db.all<Subscription>(upsertSql); // Throws TypeError: Cannot read properties of undefined (reading 'bind') const [[batchSubscription]] = await db.batch([ db.all<Subscription>(upsertSql), ]); `**Solution - Use Query Builder**:` // Use Drizzle query builder instead const [result] = await db.batch([ db.insert(schema.subscriptions) .values({ id, status }) .onConflictDoUpdate({ target: schema.subscriptions.id, set: { status } }) .returning() ]); `**Workaround - Convert to Native D1**:` import { SQLiteSyncDialect } from 'drizzle-orm/sqlite-core'; const sqliteDialect = new SQLiteSyncDialect(); const upsertQuery = sqliteDialect.sqlToQuery(upsertSql); const [result] = await D1.batch([ D1.prepare(upsertQuery.sql).bind(...upsertQuery.params), ]);
wrangler d1 migrations apply only looks for files directly in the configured directory. Prevention: Flatten migrations with post-generation script# Drizzle 1.0 beta generates this: migrations/ 20260116123456_random/ migration.sql 20260117234567_another/ migration.sql # But wrangler expects this: migrations/ 20260116123456_random.sql 20260117234567_another.sql `**Detection**:` npx wrangler d1 migrations apply my-db --remote # Output: "No migrations found" (even though migrations exist) `**Solution - Post-Generation Script**:` // scripts/flatten-migrations.ts import fs from 'fs/promises'; import path from 'path'; const migrationsDir = './migrations'; async function flattenMigrations() { const entries = await fs.readdir(migrationsDir, { withFileTypes: true }); for (const entry of entries) { if (entry.isDirectory()) { const sqlFile = path.join(migrationsDir, entry.name, 'migration.sql'); const flatFile = path.join(migrationsDir, `${entry.name}.sql`); // Move migration.sql out of folder await fs.rename(sqlFile, flatFile); // Remove empty folder await fs.rmdir(path.join(migrationsDir, entry.name)); console.log(`Flattened: ${entry.name}/migration.sql → ${entry.name}.sql`); } } } flattenMigrations().catch(console.error); `**package.json Integration**:` { "scripts": { "db:generate": "drizzle-kit generate", "db:flatten": "tsx scripts/flatten-migrations.ts", "db:migrate": "npm run db:generate && npm run db:flatten && wrangler d1 migrations apply my-db" } } `**Workaround Until Fixed**: Always run the flatten script after generating migrations:` npx drizzle-kit generate tsx scripts/flatten-migrations.ts npx wrangler d1 migrations apply my-db --remote
flat: true config option (not yet implemented).// ❌ DON'T: Use traditional transactions (fails with D1_ERROR) await db.transaction(async (tx) => { /* ... */ }); // ✅ DO: Use D1 batch API const results = await db.batch([ db.insert(users).values({ email: 'test@example.com', name: 'Test' }), db.insert(posts).values({ title: 'Post', content: 'Content', authorId: 1 }), ]); // With error handling try { await db.batch([...]); } catch (error) { console.error('Batch failed:', error); // Manual cleanup if needed }
./scripts/check-versions.shChecking Drizzle ORM versions... ✓ drizzle-orm: 0.44.7 (latest) ✓ drizzle-kit: 0.31.5 (latest)
drizzle-orm@0.45.1 - ORM runtimedrizzle-kit@0.31.8 - CLI tool for migrationsbetter-sqlite3@12.4.6 - For local SQLite development@cloudflare/workers-types@4.20251125.0 - TypeScript types/drizzle-team/drizzle-orm-docs{ "dependencies": { "drizzle-orm": "^0.45.1" }, "devDependencies": { "drizzle-kit": "^0.31.8", "@cloudflare/workers-types": "^4.20260103.0", "better-sqlite3": "^12.5.0" } }