neon-drizzle

Install drizzle-orm, @neondatabase/serverless, and drizzle-kit, then provision a Neon database and write the connection string to your environment file. Create a drizzle.config.ts with explicit dotenv loading, define your schema, and run drizzle-kit generate followed by drizzle-kit migrate.

Use the HTTP adapter for serverless and edge environments like Vercel, Cloudflare Workers, and AWS Lambda. Use the WebSocket adapter for long-lived Node.js servers like Express or Fastify when you need transactions, prepared statements, and connection pooling.

This happens because drizzle-kit runs as a separate process and does not inherit your environment variables. Fix it by adding dotenv config with an explicit path in drizzle.config.ts, such as config({ path: '.env.local' }), matching your actual environment file name.

Yes, Drizzle can coexist with Prisma, TypeORM, or other ORMs by keeping it in an isolated directory and exporting the connection under a distinct name. You can define schemas for new tables only, or mirror existing tables to gradually migrate queries without running conflicting migrations.

No, the HTTP adapter does not support transactions, prepared statements, or streaming. Use batch operations for multiple writes, or switch to the WebSocket adapter with a connection pool if your application requires atomic transactions.

Drizzle interprets renames as a drop plus add, which deletes data. Generate the migration, then manually edit the SQL file to use ALTER TABLE ... RENAME COLUMN instead before applying it with drizzle-kit migrate.