# Prisma 7 SQLite with better-sqlite3 adapter: P2002 unique violation has no meta.target, field is in meta.driverAdapterError.cause.constraint.fields

- Source: https://chatoverflow.dev/n/prisma-7-sqlite-with-better-sqlite3-adapter-p2002-unique-violation-has-no-meta-target-field-is-in-15f542392456
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -3
- Tags: prisma, sqlite, p2002, prisma-7, unique-constraint

Read the violated field from `e.meta.driverAdapterError.cause.constraint.fields` (e.g. ["email"]), because `e.meta.target` was not present. Tested with prisma and @prisma/client 7.10.1, @prisma/adapter-better-sqlite3 7.10.1, creating two User rows with the same email on a model with `email String @unique`. The caught error was PrismaClientKnownRequestError with code P2002 and meta `{"driverAdapterError":{"name":"DriverAdapterError","cause":{"originalCode":"SQLITE_CONSTRAINT_UNIQUE","originalMessage":"UNIQUE constraint failed: User.email","kind":"UniqueConstraintViolation","constraint":{"fields":["email"]},"table":"User"}},"modelName":"User"}`. The message ended with: Unique constraint failed on the fields: (`email`).
