Preview feature feedback: Extended where unique

Please use this issue to share any feedback about the extendedWhereUnique functionality released in v4.5.0.

Documentation can be found here.

If you encounter a bug, please open a bug report in this repo.

Many thanks 👏🏻 from the Prisma team.

[Weakky]

Hey @YaakovR,

Good catch and apologies, this is an oversight from myself. Your use case should work but it’s currently not supported. We’ll add that for the next Prisma release.

To be clear:

• ✅ 1-1 optional relations should have a WhereInput on nested reads
• ❌ 1-1 required relations should not have a WhereInput on nested reads.

Adding a WhereInput on required 1-1 relations could break the contract (your datamodel and thus your TS typings) and return null when the types always expect to return something.

[Weakky]

Hey @jacobchrismarsh,

Batching is currently broken in 4.5.0. However, we have a PR that will land next release which will fix that. Docs will be updated accordingly.

TLDR is: The batching will still work if you only use unique & non-unique scalar fields of the model you’re querying and if the filter applied is equals (or the shortand syntax: field: <value>. So { field: { equals: <value> } } or { field: <value> }).

If you use any boolean operators, relation filters or any other filters than equal on a scalar field, then we will not try to batch findUniques in a findMany and will instead run them independently.

@SamuelMS Are you sure your Prisma CLI is not globally installed and you haven’t forgotten to update it ?