docs
docs copied to clipboard
Document use of `findUnique` with MongoDB composite types
Describe this PR
Added examples of using findUnique
with a multi-field constraint containing a composite type to:
- the client reference entry for
findUnique
- Names in the underlying database concepts page
Changes
What issue does this fix?
Fixes #3453
Any other relevant information
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Updated |
---|---|---|---|
docs | ✅ Ready (Inspect) | Visit Preview | Aug 26, 2022 at 11:25AM (UTC) |
Deploy Preview for prisma2-docs ready!
Name | Link |
---|---|
Latest commit | 9b9170c3f7770fd0d0dad8a9fff28d911909300f |
Latest deploy log | https://app.netlify.com/sites/prisma2-docs/deploys/62eb9cb441a33900088519e6 |
Deploy Preview | https://deploy-preview-3565--prisma2-docs.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
This PR changes the following pages (Netlify/Vercel Preview Deploy links):
Changed Netlify links
- /docs/concepts/components/prisma-schema/names-in-underlying-database (currently)
- /docs/concepts/components/prisma-client/composite-types (currently)
- /docs/reference/api-reference/prisma-client-reference (currently)
Changed Vercel links
- /docs/concepts/components/prisma-schema/names-in-underlying-database (currently)
- /docs/concepts/components/prisma-client/composite-types (currently)
- /docs/reference/api-reference/prisma-client-reference (currently)
(Note that links will only be valid after Netlify/Vercel preview deploy succeeded)