database-orm-expert

Database ORM Expert (Prisma 6 + Drizzle ORM Edition)

English | Bahasa Indonesia

---

English

Description

Design schemas, select ORMs, execute migrations, optimize queries, and implement type-safe SQL patterns. Prioritize Prisma 6 and Drizzle ORM. Implement connection pooling for production workloads.

Trigger Conditions

• Designing or migrating a database schema.
• Choosing between Prisma, Drizzle ORM, or TypeORM.
• Writing complex queries with joins, aggregations, or pagination.
• Optimizing slow queries or N+1 problems.
• Setting up database migrations in CI/CD pipelines.
• Implementing Row Level Security (RLS) patterns.
• Working with PostgreSQL, MySQL, SQLite, or PlanetScale.

Orchestration & Integration

• js-backend-expert: For Node/Bun/Deno backend implementations integrating these ORMs.
• edge-serverless-db-expert: For edge/serverless connections (e.g., Supabase, Neon, Turso).
• database-migration-versioning-expert: For advanced migration strategies and CI/CD pipelines.

---

ORM Selection Guide

Criteria	Prisma 6	Drizzle ORM	TypeORM
Type Safety	Schema-generated types	SQL-like, inferred types	Decorator-based
Bundle Size	Heavy (binary client)	Lightweight (<35KB)	Medium
Query Style	Fluent ORM API	SQL-first, composable	ActiveRecord / QueryBuilder
Edge Runtime	Prisma Accelerate needed	Native edge support	No
Migrations	prisma migrate dev	drizzle-kit push/migrate	synchronize (dev only)
Best For	Rapid prototyping, teams	Production edge, monorepos	Legacy NestJS projects

Recommendation: Use Drizzle ORM for edge-compatible apps and performance-critical systems. Use Prisma 6 for teams that prefer a schema-first DX and rich Studio tooling.

---

Prisma 6 — Best Practices

Schema Design

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["relationJoins", "nativeDistinct"]
}

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL") // for Supabase Pooler
}

model User {
  id        String    @id @default(cuid())
  email     String    @unique
  name      String?
  role      Role      @default(USER)
  posts     Post[]
  createdAt DateTime  @default(now())
  updatedAt DateTime  @updatedAt

  @@index([email])
  @@map("users")
}

model Post {
  id          String   @id @default(cuid())
  title       String
  content     String?
  published   Boolean  @default(false)
  authorId    String
  author      User     @relation(fields: [authorId], references: [id], onDelete: Cascade)
  publishedAt DateTime?

  @@index([authorId, published])
  @@map("posts")
}

enum Role {
  USER
  ADMIN
  SUPER_ADMIN
}