Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 050-prisma-client-reference.mdx #6462

Merged
merged 1 commit into from
Nov 27, 2024
Merged

Update 050-prisma-client-reference.mdx #6462

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions content/200-orm/500-reference/050-prisma-client-reference.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -627,16 +627,15 @@ We introduced `findUniqueOrThrow` in v4.0.0. It replaces the [`rejectOnNotFound`

:::

`findUniqueOrThrow` retrieves a single data record similarly to [`findUnique()`](#findunique). However, if no record is found, it throws a `NotFoundError` with a message like: `No <Model> found`.

Here’s an example of how it works:
`findUniqueOrThrow` retrieves a single data record similarly to [`findUnique()`](#findunique). However, if no record is found, it throws a `NotFoundError` with a message like: `No <Model> found`. Here’s an example of its usage:

```ts
await prisma.user.findUniqueOrThrow({
where: {
id: 1,
},
});
```

`findUniqueOrThrow` differs from `findUnique()` as follows:

Expand Down
Loading