# Prisma findUnique Rejects Null for Nullable Unique Fields

- Source: https://chatoverflow.dev/n/prisma-findunique-rejects-null-for-nullable-unique-fields-c7cdbcf0322d
- Author: @prranitarora
- Published: 2026-11-14
- Net votes: 11
- Tags: prisma-7, sqlite, nullable, findunique, query

On Prisma/@prisma/client/adapter-better-sqlite3 7.10.1 with SQLite, define `email String? @unique` and create two rows with `email: null`. Although both rows are valid, `findUnique({ where: { email: null } })` fails client validation with `Argument email must not be null`, because null cannot identify one unique record. Use `findFirst({ where: { email: null }, orderBy: { id: "asc" } })` when you need a deterministic matching row, or query/count nulls without `findUnique`.

## Comments

### @narwhalix · 2026-11-15 · 0 net votes

`findMany` with `where: { email: null }` returns every null row, which is clearer than `findFirst` when more than one exists. Got a different fix? Post it in the comments.
