[findFirst] cannot take negative one

[jay-l-e-e]

Bug description

PrismaClientKnownRequestError: \nInvalid `prisma.audit.findFirst()` invocation:\n\n\nInput error. The 'findFirst' operation cannot be used with a 'take' argument that isn't 1

model.findFirst({ ..., take: -1 });

Severity

🚨 Critical: Data loss, app crash, security issue

Reproduction

Just try findFirst with take: -1

Expected vs. Actual Behavior

Expected: No error
Actual: Error

Frequency

Consistently reproducible

Does this occur in development or production?

Production and development

Is this a regression?

I'm not sure, but it seems to have worked before version 6.9.0.

Workaround

IDK

Prisma Schema & Queries

model Audit {
  id         Bytes       @id @database.ByteA
}

await Audit.findFirst({
  ...findConditions,
  skip: 0,
  take: before ? -1 : 1,
});

Prisma Config

import { join } from 'node:path';

import 'dotenv/config';

import type { PrismaConfig } from 'prisma';

export default {
  schema: join('sources', 'domains'),
  migrations: {
    path: join('sources', 'migrations'),
  },
} satisfies PrismaConfig;

Logs & Debug Info

PrismaClientKnownRequestError: \nInvalid `prisma.audit.findFirst()` invocation:\n\n\nInput error. The 'findFirst' operation cannot be used with a 'take' argument that isn't 1

Environment & Setup

• OS: MacOs, Windows, Linux Alpine
• Database: PostgreSQL
• Node.js version: 22 LTS

Prisma Version

6.16.1

[jay-l-e-e]

Guys you can find the official documentation for this:
Get the first Post record where the title starts with A test, resverse the list with take

[ann20502]

I encountered the same issue after updating my project from 6.2.1 to 6.16.1.
Reverting to 6.7.0 is my temporary fix, as any version above 6.7.0 seems to have the same problem.