2.16.0 and Refactor: Prisma Client API reference

content/100-getting-started/01-quickstart.mdx

@@ -285,7 +285,7 @@ This should print the following result to your terminal:
 ]
 ```
 
-One of the main features of Prisma Client is the ease of working with relations. You can retrieve the `posts` of each user by using the [`include`](../concepts/components/prisma-client/field-selection#include) option. Adjust your code to look as follows:
+One of the main features of Prisma Client is the ease of working with relations. You can retrieve the `posts` of each user by using the [`include`](../concepts/components/prisma-client/select-fields#include) option. Adjust your code to look as follows:
 
 <SwitchTech technologies={['typescript']}>
 

content/100-getting-started/02-setup-prisma/01-add-to-existing-project.mdx

@@ -4,6 +4,7 @@ title: 'Add to existing project'
 # metaDescription: 'Learn how to add Prisma to an existing Node.js or TypeScript project by connecting it to your database and generating Prisma Client for database access.'
 langSwitcher: ['typescript', 'node']
 dbSwitcher: ['postgres', 'mysql']
+duration: '15 min' 
 techMetaTitles: [
   {name: 'node-postgres', value: 'Add to existing project (Node.js & PostgreSQL)'},
   {name: 'typescript-postgres', value: 'Add to existing project (TypeScript & PostgreSQL)'},
@@ -372,7 +373,7 @@ Right now, there's a few minor "issues" with the data model:
 - The `Post` and `Profile` relation fields on `User` as well as the `User` relation field on `Profile` are all uppercased. To adhere to Prisma's [naming conventions](../../reference/api-reference/prisma-schema-reference#naming-conventions-1) <span class="api"></span>, both fields should be lowercased to `post`, `profile` and `user`.
 - Even after lowercasing, the `post` field on `User` is still slightly misnamed. That's because it actually refers to a [list](../../concepts/components/prisma-schema/data-model#type-modifiers) of posts – a better name therefore would be the plural form: `posts`.
 
-These changes are relevant for the generated Prisma Client API where using lowercased relation fields `author`, `posts`, `profile` and `user` will feel more natural and idiomatic to JavaScript/TypeScript developers. You can therefore [configure your Prisma Client API](../../concepts/components/prisma-client/configuring-the-prisma-client-api).
+These changes are relevant for the generated Prisma Client API where using lowercased relation fields `author`, `posts`, `profile` and `user` will feel more natural and idiomatic to JavaScript/TypeScript developers. You can therefore [configure your Prisma Client API](../../concepts/components/prisma-client/generating-the-prisma-client/customizing-the-prisma-client-api).
 
 Because [relation fields](../../concepts/components/prisma-schema/relations#relation-fields) are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database:
 
@@ -451,7 +452,7 @@ const user = await prisma.myUser.create({
 })
 ```
 
-Learn more about this on the [Configuring your Prisma Client API](../../concepts/components/prisma-client/configuring-the-prisma-client-api) page.
+Learn more about this on the [Configuring your Prisma Client API](../../concepts/components/prisma-client/generating-the-prisma-client/customizing-the-prisma-client-api) page.
 
 ## Install and generate Prisma Client
 
@@ -655,7 +656,7 @@ async function main() {
 
 This code creates a new `User` record together with new `Post` and `Profile` records using a [nested write](../../concepts/components/prisma-client/relation-queries#nested-writes) query. The `User` record is connected to the two other ones via the `Post.author` ↔ `User.posts` and `Profile.user` ↔ `User.profile` [relation fields](../../concepts/components/prisma-schema/relations#relation-fields) respectively.
 
-Notice that you're passing the [`include`](../../concepts/components/prisma-client/field-selection#include) option to `findMany` which tells Prisma Client to include the `posts` and `profile` relations on the returned `User` objects.
+Notice that you're passing the [`include`](../../concepts/components/prisma-client/select-fields#include) option to `findMany` which tells Prisma Client to include the `posts` and `profile` relations on the returned `User` objects.
 
 <SwitchTech technologies={['typescript', '*']}>
 

content/100-getting-started/02-setup-prisma/02-start-from-scratch.mdx

@@ -4,6 +4,7 @@ title: 'Start from scratch'
 # metaDescription: 'Learn how to create a new Node.js or TypeScript project from scratch by connecting Prisma to your database and generating Prisma Client for database access.'
 langSwitcher: ['typescript', 'node']
 dbSwitcher: ['postgres', 'mysql']
+duration: '15 min'  
 techMetaTitles:
   [
     { name: 'node-postgres', value: 'Start from scratch | Node.js & PostgreSQL' },
@@ -583,7 +584,7 @@ async function main() {
 
 This code creates a new `User` record together with new `Post` and `Profile` records using a [nested write](../../concepts/components/prisma-client/relation-queries#nested-writes) query. The `User` record is connected to the two other ones via the `Post.author` ↔ `User.posts` and `Profile.user` ↔ `User.profile` [relation fields](../../concepts/components/prisma-schema/relations#relation-fields) respectively.
 
-Notice that you're passing the [`include`](../../concepts/components/prisma-client/field-selection#include) option to `findMany` which tells Prisma Client to include the `posts` and `profile` relations on the returned `User` objects.
+Notice that you're passing the [`include`](../../concepts/components/prisma-client/select-fields#include) option to `findMany` which tells Prisma Client to include the `posts` and `profile` relations on the returned `User` objects.
 
 Run the code with this command:
 

content/100-getting-started/02-setup-prisma/index.mdx

@@ -2,8 +2,8 @@
 title: 'Set up Prisma'
 metaTitle: ''
 metaDescription: ''
-duration: '15 min'
 toc: false
+staticLink: true
 ---
 
 <TopBlock>

content/200-concepts/050-overview/100-what-is-prisma/index.mdx

@@ -200,7 +200,7 @@ The typical workflow when using **SQL migrations and introspection** looks as fo
 
 1. Manually adjust your database schema using SQL
 1. (Re-)introspect your database
-1. Optionally (re-)configure your Prisma Client API ([learn more](../../components/prisma-client/configuring-the-prisma-client-api))
+1. Optionally (re-)configure your Prisma Client API ([learn more](../../components/prisma-client/generating-the-prisma-client/customizing-the-prisma-client-api))
 1. (Re-)generate Prisma Client
 1. Use Prisma Client in your application code to access your database
 

content/200-concepts/100-components/01-prisma-schema/02-data-sources.mdx

@@ -42,7 +42,7 @@ Prisma uses the provider that is compatible with the the value of the `url` fiel
 
 Prisma resolves SSL certificates relative to the `.\prisma` directory. If your certificate files are located in the root directory, use relative paths for certificates:
 
-```prisma file=schema.prisma
+```prisma
 datasource db {
   provider = "postgresql"
   url      = "postgresql://johndoe:mypassword@localhost:5432/mydb?schema=public&sslmode=require&sslcert=../server-ca.pem&sslidentity=../client-identity.p12&sslpassword=<REDACTED>"

content/200-concepts/100-components/01-prisma-schema/04-data-model.mdx

@@ -239,7 +239,7 @@ With this model definition, Prisma automatically maps the `Comment` model to the
 
 > **Note**: You can also [`@map`](../../../reference/api-reference/prisma-schema-reference#map) <span class="api"></span> a column name or enum value, and `@@map` an enum.
 
-`@map` and `@@map` allow you to [tune the shape of your Prisma Client API](../prisma-client/configuring-the-prisma-client-api#using-map-and-map-to-rename-fields-and-models-in-the-prisma-client-api) by decoupling model and field names from table and column names in the underlying database.
+`@map` and `@@map` allow you to [tune the shape of your Prisma Client API](../prisma-client/generating-the-prisma-client/customizing-the-prisma-client-api#using-map-and-map-to-rename-fields-and-models-in-the-prisma-client-api) by decoupling model and field names from table and column names in the underlying database.
 
 ## Defining fields
 
@@ -510,7 +510,7 @@ If you do not specify an index name, introspection generates [a name based on Pr
 
 You can define enums in your data model [if they're supported by the data source you use](../../../reference/database-reference/database-features#misc).
 
-Enums are considered [scalar](#field-types) types in the Prisma data model. They're therefore [by default](../prisma-client/field-selection#the-default-selection-set) included as return values in [Prisma Client queries](../prisma-client/crud).
+Enums are considered [scalar](#field-types) types in the Prisma data model. They're therefore [by default](../prisma-client/select-fields#the-default-selection-set) included as return values in [Prisma Client queries](../prisma-client/crud).
 
 Enums are defined via the [`enum`](../../../reference/api-reference/prisma-schema-reference#enum) <span class="api"></span> block. For example, a `User` has a `Role`:
 
@@ -541,7 +541,7 @@ model Post {
 }
 ```
 
-[`cuid()`](../../../reference/api-reference/prisma-schema-reference#cuid) <span class="api"></span> and [`uuid()`](../../../reference/api-reference/prisma-schema-reference#uuid) <span class="api"></span> are implemented by Prisma and therefore are not "visible" in the underlying database schema. You can still use them when using [introspection](../introspection) by [manually changing your Prisma schema](../prisma-client/configuring-the-prisma-client-api) and [generating Prisma Client](../prisma-client/generating-prisma-client), in that case the values will be generated by Prisma's [query engine](../prisma-client/query-engine)
+[`cuid()`](../../../reference/api-reference/prisma-schema-reference#cuid) <span class="api"></span> and [`uuid()`](../../../reference/api-reference/prisma-schema-reference#uuid) <span class="api"></span> are implemented by Prisma and therefore are not "visible" in the underlying database schema. You can still use them when using [introspection](../introspection) by [manually changing your Prisma schema](../prisma-client/generating-the-prisma-client/customizing-the-prisma-client-api) and [generating Prisma Client](../prisma-client/generating-prisma-client), in that case the values will be generated by Prisma's [query engine](../prisma-client/query-engine)
 
 `autoincrement()`, `now` and `dbgenerated()` are always "implemented" on the database-level, meaning they manifest in the database schema and can be recognized through introspection.
 
@@ -581,7 +581,7 @@ const allUsers = await prisma.user.findMany()
 
 Prisma Client not only provides a query API for models, it also generates type definitions that reflect your model structures. These are part of the generated [`@prisma/client`](../prisma-client/generating-prisma-client#the-prismaclient-npm-package) node module in a file called `index.d.ts`.
 
-When using TypeScript, these type definitions ensure that all your database queries are entirely type safe and validated at compile-time (even partial queries using [`select`](../prisma-client/field-selection#select) or [`include`](../prisma-client/field-selection#include)).
+When using TypeScript, these type definitions ensure that all your database queries are entirely type safe and validated at compile-time (even partial queries using [`select`](../prisma-client/select-fields#select) or [`include`](../prisma-client/select-fields#include)).
 
 Even when using plain JavaScript, the type definitions are still included in the `@prisma/client` node module, enabling features like [IntelliSense](https://code.visualstudio.com/docs/editor/intellisense)/autocompletion in your editor.
 

content/200-concepts/100-components/01-prisma-schema/06-relations.mdx

@@ -8,7 +8,7 @@ metaDescription: 'A relation is a connection between two models in the Prisma sc
 
 A relation is a _connection_ between two models in the Prisma schema. For example, there is a one-to-many relation between `User` and `Post` because one user can have many blog posts. The following Prisma schema defines a one-to-many relation between the `User` and `Post` models. The fields involved in defining the relation are highlighted:
 
-```prisma line-number
+```prisma line-number file=schema.prisma
 model User {
   id      Int      @id @default(autoincrement())
 |  posts   Post[]
@@ -903,7 +903,7 @@ To create a one-to-one self-relation:
 
 Either side of the relation can be backed by a foreign key. In the following example, `successor` is backed by `successorId`:
 
-```prisma line-number
+```prisma line-number file=schema.prisma
 model User {
   id             Int     @default(autoincrement()) @id
   name           String?
@@ -915,7 +915,7 @@ model User {
 
 In the following example, `predecessor` is backed by `predecessorId`:
 
-```prisma line-number
+```prisma line-number file=schema.prisma
 model User {
   id             Int     @default(autoincrement()) @id
   name           String?

content/200-concepts/100-components/02-prisma-client/020-configuring-the-prisma-client-api.mdx → content/200-concepts/100-components/02-prisma-client/000-generating-prisma-client/020-customizing-the-prisma-client-api.mdx

@@ -1,6 +1,6 @@
 ---
-title: 'Configuring the Prisma Client API'
-metaTitle: 'Configuring the Prisma Client API (Reference)'
+title: 'Customizing the client'
+metaTitle: 'Customizing the client (Concepts)'
 metaDescription: 'Learn how you can decouple the naming of Prisma models from database tables to improve the ergonomics of the generated Prisma Client API.'
 ---