Master Drizzle ORM for Type-Safe Databases

Helps build type-safe, performant database layers with Drizzle ORM in TypeScript: schema design, the relational query API, Drizzle Kit migrations, and integrations with Next.js, tRPC, and serverless databases (Neon, PlanetScale, Turso, Supabase). It positions Drizzle against Prisma - Drizzle compiles to raw SQL with zero runtime overhead rather than shipping a query-engine binary, making it fit for edge runtimes and serverless environments like Cloudflare Workers, Vercel Edge, and Deno - with full type inference connecting schema, types, and queries at compile time, and a Prisma-like relational query API that resolves nested includes without N+1 problems.

npx drizzle-kit generate

It covers schema definition with pgTable and relations(), direct type inference via InferSelectModel/InferInsertModel, SQL-like select/join/aggregation queries alongside the relational db.query.* API, inserts with .returning(), batch inserts, updates, deletes, and transactions, the Drizzle Kit migration workflow (generate for migration SQL, push for dev-only direct schema sync, migrate for production, studio for a GUI browser), database client setup for Neon (HTTP), Turso/LibSQL, and PlanetScale, and performance patterns - prepared statements, db.batch() for multiple queries in one round trip, and schema-level indexing. Migration config (drizzle.config.ts) declares the schema path, output directory, SQL dialect, and database credentials that Drizzle Kit's commands read from.

Use it when setting up Drizzle in a new or existing project, designing TypeScript-first schemas, writing complex relational queries, setting up or troubleshooting Drizzle Kit migrations, integrating with Next.js App Router, tRPC, or Hono, optimizing database performance, or migrating from Prisma, TypeORM, or Knex.

Input: a database schema or query requirement in a TypeScript project using, or adopting, Drizzle. Output: typed schema definitions and relations, type-safe query code (select, relational, insert/update/delete, transaction), migration commands and config, and database-client wiring for the target backend - Neon, Turso, or PlanetScale.

Integrates with Next.js (Server Components and Server Actions), tRPC, and Hono, and with serverless Postgres, SQLite, and MySQL backends - Neon (drizzle-orm/neon-http), Turso/LibSQL (@libsql/client), and PlanetScale (drizzle-orm/planetscale-serverless) - each via its own driver import. Its best-practice rules explicitly forbid drizzle-kit push in production due to data-loss risk, favoring generate plus migrate instead, and warn that MySQL doesn't support .returning() - .execute() and reading insertId from the result is required there instead. It also warns against creating a new database connection per request in a serverless environment - use connection pooling - and troubleshoots a db.query.tableName undefined error back to the same root cause: the full schema, including relations, must be passed into drizzle() to enable the relational query API at all.

TypeScript developers setting up or optimizing a Drizzle ORM database layer, especially on serverless or edge runtimes, who need type-safe schema design and migration discipline.