Database and Prisma Structure

Prisma Overview

Jacinto's Person Search uses Prisma ORM with Neon PostgreSQL. Prisma Client handles all Create, Read, Update, and Delete operations from server actions.

Connection strings are provided through DATABASE_URL and DIRECT_URL. In production, DATABASE_URL points to Neon and DIRECT_URL is used for direct database access during migrations.

Person Model

model Person {
  id          String   @id @default(cuid())
  name        String
  email       String   @unique
  phoneNumber String   @unique
  createdAt   DateTime @default(now())
  updatedAt   DateTime @updatedAt
}

Migrations and Seed Data

Prisma migrations define schema history under prisma/migrations. Sample data is inserted with prisma/seed.ts to ensure evaluators can test search, edit, and delete flows immediately.

Server actions in app/actions/actions.ts call Prisma Client directly, so all app-level CRUD operations are backed by the database.