docs
docs copied to clipboard
prisma
fix(relations): Optional/mandatory headlines for 1-1 and 1-n
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 15, 2023 2:01pm |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
This PR changes the following pages (Vercel Preview Deploy links):
Changed Vercel links
- /docs/concepts/components/prisma-schema/relations/one-to-one-relations (currently)
- /docs/concepts/components/prisma-schema/relations/one-to-many-relations (currently)
(Note that links will only be valid after Vercel preview deploy succeeded)
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This PR probably requires the following redirects to be added to vercel.json:
- This PR does not change any pages in a way that would require a redirect.
Made some comments. TL;DR I think our terminology should be "nullable" and "non-nullable"
What I used here is established terminology in Prisma context.
- We always use "mandatory" in this context to describe them being "non optional".
- "null" is not a concept that exists in Prisma context. There things are optional or not, which is then translated to nullable on the database level.
What I used here is established terminology in Prisma context.
- We always use "mandatory" in this context to describe them being "non optional".
- "null" is not a concept that exists in Prisma context. There things are optional or not, which is then translated to nullable on the database level.
There doesn't seem to be any established terminology since we're using all of these terms across the docs.
For that reasons and because they're all interchangeable, I wouldn't let this discussion block the merging of this PR if it otherwise looks good.
The "real" solution here will be to determine one term (my vote would go to "required") that we want to use in this context and then update the docs everywhere to use that term consistently. I created an issue for that: https://github.com/prisma/docs/issues/5487
I would encourage to merge this PR regardless of the terms being use.
