feat: prisma lesson #28230
feat: prisma lesson #28230
Conversation
01zulfi
added
the
Project Node Revamp
Co-authored-by: Asartea <76259120+Asartea@users.noreply.github.com>
|
|
||
| There's a bunch of new stuff up here. Prisma schema files are written in Prisma Schema Language. You can see how not only there are column definitions for the table, but also a relation to another table defined within the `Message` model. You'll learn more about this in the assignment readings. | ||
|
|
||
| This schema file lives in your codebase and is tracked by version control. You can guess by now how useful this is. |
There was a problem hiding this comment.
I think it might be good to mention what the schema file is (that it has a specific naming convention) and that there can be multiple schema files in Prisma. e.g. from the docs:
It is typically a single file called schema.prisma (or multiple files with .prisma file extension) that is stored in a defined but customizable location.
There was a problem hiding this comment.
I purposefully kept out this information, since learners will only ever need one schema file for the projects they tackle in the curriculum. They do learn about the naming convention and the multiple files stuff in the linked documentation in the assignment section.
Co-authored-by: Christian Medina <117231596+cmedina-dev@users.noreply.github.com>
Co-authored-by: Christian Medina <117231596+cmedina-dev@users.noreply.github.com>
Co-authored-by: MaoShizhong <122839503+MaoShizhong@users.noreply.github.com>
Co-authored-by: MaoShizhong <122839503+MaoShizhong@users.noreply.github.com>
Co-authored-by: MaoShizhong <122839503+MaoShizhong@users.noreply.github.com>
Co-authored-by: MaoShizhong <122839503+MaoShizhong@users.noreply.github.com>
Co-authored-by: MaoShizhong <122839503+MaoShizhong@users.noreply.github.com>
|
|
||
| #### So much more code | ||
|
|
||
| You need a `SELECT` statement? Cool, write a query. Need a `SELECT` statement for a different table? Write another query. Or if your programmer senses are tingling, you could create a utility function for `SELECT`. But now you need a `SELECT` statement for specific columns? You'll have to modify the utility function. What about filters and sorting? You get the point. |
There was a problem hiding this comment.
Nit: sorry I missed this one earlier
| You need a `SELECT` statement? Cool, write a query. Need a `SELECT` statement for a different table? Write another query. Or if your programmer senses are tingling, you could create a utility function for `SELECT`. But now you need a `SELECT` statement for specific columns? You'll have to modify the utility function. What about filters and sorting? You get the point. | |
| Do you need a `SELECT` statement? Cool, write a query. Need a `SELECT` statement for a different table? Write another query. Or if your programmer senses are tingling, you could create a utility function for `SELECT`. But now you need a `SELECT` statement for specific columns? You'll have to modify the utility function. What about filters and sorting? You get the point. |
There was a problem hiding this comment.
I feel "You need a SELECT statement?" reads better than creating a question-ish tone. I'll reserve this change unless we get anyone else's objection.
There was a problem hiding this comment.
Both are fine. The first has a more casual tone but is otherwise still fine
Co-authored-by: Asartea <76259120+Asartea@users.noreply.github.com>
Because
#27925
This PR
#27925
Issue
Closes #27925
Additional Information
Pull Request Requirements
location of change: brief description of changeformat, e.g.Intro to HTML and CSS lesson: Fix link textBecausesection summarizes the reason for this PRThis PRsection has a bullet point list describing the changes in this PRIssuesection