From b6e75c2aa13af5579d6dfeb3c1308ad6e7a9c432 Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Mon, 3 Jun 2024 11:57:57 -0500 Subject: [PATCH 01/18] add initial docs for multi-file Prisma schema and clean up references to singular Prisma schema file --- content/100-getting-started/01-quickstart.mdx | 2 +- .../150-introspection-node-cockroachdb.mdx | 2 +- .../150-introspection-node-mysql.mdx | 2 +- .../150-introspection-node-planetscale.mdx | 2 +- .../150-introspection-node-postgresql.mdx | 2 +- .../150-introspection-node-sqlserver.mdx | 2 +- ...0-introspection-typescript-cockroachdb.mdx | 2 +- .../150-introspection-typescript-mysql.mdx | 2 +- ...0-introspection-typescript-planetscale.mdx | 2 +- ...50-introspection-typescript-postgresql.mdx | 2 +- ...150-introspection-typescript-sqlserver.mdx | 2 +- .../100-introduction/100-what-is-prisma.mdx | 2 +- .../04-is-prisma-an-orm.mdx | 4 +- .../500-databases/300-postgresql.mdx | 2 +- .../050-overview/500-databases/400-mysql.mdx | 2 +- .../050-overview/500-databases/500-sqlite.mdx | 2 +- .../500-databases/600-mongodb.mdx | 10 +-- .../500-databases/800-sql-server/index.mdx | 2 +- .../500-databases/840-cockroachdb.mdx | 6 +- .../10-overview/03-generators.mdx | 2 +- .../100-prisma-schema/10-overview/index.mdx | 46 +++++++----- .../20-data-model/40-views.mdx | 2 +- .../20-data-model/60-multi-schema.mdx | 4 +- .../20-data-model/90-multiple-files.mdx | 71 +++++++++++++++++++ .../100-prisma-schema/50-introspection.mdx | 4 +- .../80-postgresql-extensions.mdx | 2 +- .../400-deploy-to-aws-lambda.mdx | 4 +- .../070-migration-histories.mdx | 2 +- .../300-workflows/100-team-development.mdx | 4 +- .../120-native-database-functions.mdx | 2 +- .../200-prisma-cli-reference.mdx | 4 +- .../050-client-preview-features.mdx | 1 + .../600-upgrading-to-prisma-5/index.mdx | 2 +- .../700-upgrading-to-prisma-4.mdx | 2 +- .../03-upgrading-the-prisma-layer-mysql.mdx | 2 +- ...-upgrading-the-prisma-layer-postgresql.mdx | 2 +- .../05-upgrading-prisma-binding-to-nexus.mdx | 2 +- .../01-migrate-from-typeorm.mdx | 4 +- .../02-migrate-from-sequelize.mdx | 4 +- .../03-migrate-from-mongoose.mdx | 4 +- .../04-migrate-from-drizzle.mdx | 4 +- .../040-env-files.mdx | 2 +- docusaurus.config.ts | 2 +- 43 files changed, 155 insertions(+), 75 deletions(-) create mode 100644 content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx diff --git a/content/100-getting-started/01-quickstart.mdx b/content/100-getting-started/01-quickstart.mdx index bd6495ae0b..837b177015 100644 --- a/content/100-getting-started/01-quickstart.mdx +++ b/content/100-getting-started/01-quickstart.mdx @@ -63,7 +63,7 @@ Finally, set up Prisma ORM with the `init` command of the Prisma CLI: npx prisma init --datasource-provider sqlite ``` -This creates a new `prisma` directory with your Prisma schema file and configures SQLite as your database. You're now ready to model your data and create your database with some tables. +This creates a new `prisma` directory with a `prisma.schema` file and configures SQLite as your database. You're now ready to model your data and create your database with some tables. ## 2. Model your data in the Prisma schema diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx index f9bc98bf11..788ba00c96 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx @@ -83,7 +83,7 @@ npx prisma db pull This command reads the environment variable used to define the `url` in your `schema.prisma`, `DATABASE_URL`, that in our case is set in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a Prisma data model. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx index d33b1d28c0..b5c76da70e 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx @@ -81,7 +81,7 @@ npx prisma db pull This command reads the `DATABASE_URL` environment variable that's defined in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a Prisma data model. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx index a743a74f68..2f4b0c4955 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx @@ -89,7 +89,7 @@ npx prisma db pull This command reads the `DATABASE_URL` environment variable that's defined in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a Prisma data model. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx index d1781966bc..2a5febf211 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx @@ -84,7 +84,7 @@ npx prisma db pull This command reads the `DATABASE_URL` environment variable that's defined in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a data model in your Prisma schema. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database with Prisma ORM](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx index 3c67e5be75..9941291dd4 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx @@ -91,7 +91,7 @@ npx prisma db pull This command reads the `DATABASE_URL` environment variable that's defined in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a Prisma data model. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx index 8f0d54e1ff..bd3d478c53 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx @@ -84,7 +84,7 @@ npx prisma db pull This command reads the environment variable used to define the `url` in your `schema.prisma`, `DATABASE_URL`, that in our case is set in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a Prisma data model. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx index 5c96ab1b90..3d420aeaaa 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx @@ -82,7 +82,7 @@ npx prisma db pull This command reads the `DATABASE_URL` environment variable that's defined in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a Prisma data model. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx index ed7a92cbc2..bfe87aadc1 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx @@ -89,7 +89,7 @@ npx prisma db pull This command reads the `DATABASE_URL` environment variable that's defined in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a Prisma data model. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx index 6c04f4ce06..d06110d433 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx @@ -83,7 +83,7 @@ npx prisma db pull This command reads the `DATABASE_URL` environment variable that's defined in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a data model in your Prisma schema. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database with Prisma ORM](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx index b8a21c5b53..3ac7190407 100644 --- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx +++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx @@ -91,7 +91,7 @@ npx prisma db pull This command reads the `DATABASE_URL` environment variable that's defined in `.env` and connects to your database. Once the connection is established, it introspects the database (i.e. it _reads the database schema_). It then translates the database schema from SQL into a Prisma data model. -After the introspection is complete, your Prisma schema file was updated: +After the introspection is complete, your Prisma schema is updated: ![Introspect your database](/img/getting-started/prisma-db-pull-generate-schema.png) diff --git a/content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx b/content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx index 177fa3a90a..98fdb45de3 100644 --- a/content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx +++ b/content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx @@ -34,7 +34,7 @@ Prisma Client can be used in _any_ Node.js (supported versions) or TypeScript ba ### The Prisma schema -Every project that uses a tool from the Prisma ORM toolkit starts with a [Prisma schema file](/orm/prisma-schema). The Prisma schema allows developers to define their _application models_ in an intuitive data modeling language. It also contains the connection to a database and defines a _generator_: +Every project that uses a tool from the Prisma ORM toolkit starts with a [Prisma schema](/orm/prisma-schema). The Prisma schema allows developers to define their _application models_ in an intuitive data modeling language. It also contains the connection to a database and defines a _generator_: diff --git a/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx b/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx index de96103532..393de9de00 100644 --- a/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx +++ b/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx @@ -182,7 +182,7 @@ Prisma ORM is a **next-generation ORM** that makes working with databases easy f > **Note:** Since Prisma Client is the most prominent tool, we often refer to it as simply Prisma. -The three tools use the [Prisma schema](/orm/prisma-schema) as a single source of truth for the database schema, your application's object schema, and the mapping between the two. It's defined by you and is your main configuration file for Prisma ORM. +The three tools use the [Prisma schema](/orm/prisma-schema) as a single source of truth for the database schema, your application's object schema, and the mapping between the two. It's defined by you and is your main way of configuring Prisma ORM. Prisma ORM makes you productive and confident in the software you're building with features such as _type safety_, rich auto-completion, and a natural API for fetching relations. @@ -440,7 +440,7 @@ In summary, Prisma ORM is a new kind of Data Mapper ORM that differs from tradit Unlike traditional ORMs, with Prisma ORM, you define the Prisma schema – a declarative single source of truth for the database schema and application models. All queries in Prisma Client return plain JavaScript objects which makes the process of interacting with the database a lot more natural as well as more predictable. -Prisma ORM supports two main workflows for starting new projects and adopting in an existing project. For both workflows, the Prisma schema is the main configuration file. +Prisma ORM supports two main workflows for starting new projects and adopting in an existing project. For both workflows, your main avenue for configuration is via the Prisma schema. Like all abstractions, both Prisma ORM and other ORMs hide away some of the underlying details of the database with different assumptions. diff --git a/content/200-orm/050-overview/500-databases/300-postgresql.mdx b/content/200-orm/050-overview/500-databases/300-postgresql.mdx index 340f10e026..dad04752e9 100644 --- a/content/200-orm/050-overview/500-databases/300-postgresql.mdx +++ b/content/200-orm/050-overview/500-databases/300-postgresql.mdx @@ -15,7 +15,7 @@ By default, the PostgreSQL connector contains a database driver responsible for ## Example -To connect to a PostgreSQL database server, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema file](/orm/prisma-schema): +To connect to a PostgreSQL database server, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema](/orm/prisma-schema): ```prisma file=schema.prisma showLineNumbers datasource db { diff --git a/content/200-orm/050-overview/500-databases/400-mysql.mdx b/content/200-orm/050-overview/500-databases/400-mysql.mdx index 68f7b01ab2..6cd4bab235 100644 --- a/content/200-orm/050-overview/500-databases/400-mysql.mdx +++ b/content/200-orm/050-overview/500-databases/400-mysql.mdx @@ -15,7 +15,7 @@ By default, the MySQL connector contains a database driver responsible for conne ## Example -To connect to a MySQL database server, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema file](/orm/prisma-schema): +To connect to a MySQL database server, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema](/orm/prisma-schema): ```prisma file=schema.prisma showLineNumbers datasource db { diff --git a/content/200-orm/050-overview/500-databases/500-sqlite.mdx b/content/200-orm/050-overview/500-databases/500-sqlite.mdx index 83ccbff260..9e8dd99f9a 100644 --- a/content/200-orm/050-overview/500-databases/500-sqlite.mdx +++ b/content/200-orm/050-overview/500-databases/500-sqlite.mdx @@ -15,7 +15,7 @@ By default, the SQLite connector contains a database driver responsible for conn ## Example -To connect to a SQLite database file, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [schema file](/orm/prisma-schema): +To connect to a SQLite database file, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema](/orm/prisma-schema): ```prisma file=schema.prisma showLineNumbers datasource db { diff --git a/content/200-orm/050-overview/500-databases/600-mongodb.mdx b/content/200-orm/050-overview/500-databases/600-mongodb.mdx index 070e7ae9bf..dc41f9339b 100644 --- a/content/200-orm/050-overview/500-databases/600-mongodb.mdx +++ b/content/200-orm/050-overview/500-databases/600-mongodb.mdx @@ -33,11 +33,11 @@ Some aspects of using Prisma ORM with MongoDB are the same as when using Prisma - connect to your database, using the [`mongodb` database connector](/orm/overview/databases) - use [Introspection](/orm/prisma-schema/introspection) for existing projects if you already have a MongoDB database - use [`db push`](/orm/prisma-migrate/workflows/prototyping-your-schema) to push changes in your schema to the database -- use [Prisma Client](/orm/prisma-client) in your application to query your database in a type safe way based on your Prisma Schema +- use [Prisma Client](/orm/prisma-client) in your application to query your database in a type safe way based on your Prisma schema ## Differences to consider -MongoDB's document-based structure and flexible schemas means that using Prisma ORM with MongoDB differs from using it with a relational database in a number of ways. These are some areas where there are differences that you need to be aware of: +MongoDB's document-based structure and flexible schema means that using Prisma ORM with MongoDB differs from using it with a relational database in a number of ways. These are some areas where there are differences that you need to be aware of: - **Defining IDs**: MongoDB documents have an `_id` field (that often contains an [ObjectID](https://www.mongodb.com/docs/manual/reference/bson-types/#std-label-objectid)). Prisma ORM does not support fields starting with `_`, so this needs to be mapped to a Prisma ORM field using the `@map` attribute. For more information, see [Defining IDs in MongoDB](/orm/prisma-schema/data-model/models#defining-ids-in-mongodb). @@ -55,7 +55,7 @@ This section provides instructions for how to carry out tasks that require steps ### How to migrate existing data to match your Prisma schema -Migrating your database over time is an important part of the development cycle. During development, you will need to update your Prisma schema file (for example, to add new fields), then update the data in your development environment’s database, and eventually push both the updated schema and the new data to the production database. +Migrating your database over time is an important part of the development cycle. During development, you will need to update your Prisma schema (for example, to add new fields), then update the data in your development environment’s database, and eventually push both the updated schema and the new data to the production database. @@ -127,7 +127,7 @@ As an example, take a MongoDB database with two collections, `User` and `Post`. - `title` field with a type of `string` - `userId` with a type of `objectID` -On introspection with `db pull`, this is pulled in to the Prisma schema file as follows: +On introspection with `db pull`, this is pulled in to the Prisma schema as follows: ```prisma file=prisma/schema.prisma showLineNumbers model Post { @@ -356,7 +356,7 @@ For more information on how to set up and manage a MongoDB database, see the [Pr ## Example -To connect to a MongoDB server, configure the [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema file](/orm/prisma-schema): +To connect to a MongoDB server, configure the [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema](/orm/prisma-schema): ```prisma file=schema.prisma showLineNumbers datasource db { diff --git a/content/200-orm/050-overview/500-databases/800-sql-server/index.mdx b/content/200-orm/050-overview/500-databases/800-sql-server/index.mdx index 5e64df24db..d7969841ec 100644 --- a/content/200-orm/050-overview/500-databases/800-sql-server/index.mdx +++ b/content/200-orm/050-overview/500-databases/800-sql-server/index.mdx @@ -14,7 +14,7 @@ The Microsoft SQL Server data source connector connects Prisma ORM to a [Microso ## Example -To connect to a Microsoft SQL Server database, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema file](/orm/prisma-schema): +To connect to a Microsoft SQL Server database, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema](/orm/prisma-schema): ```prisma file=schema.prisma showLineNumbers datasource db { diff --git a/content/200-orm/050-overview/500-databases/840-cockroachdb.mdx b/content/200-orm/050-overview/500-databases/840-cockroachdb.mdx index c433d1c827..1d6b8e203c 100644 --- a/content/200-orm/050-overview/500-databases/840-cockroachdb.mdx +++ b/content/200-orm/050-overview/500-databases/840-cockroachdb.mdx @@ -33,7 +33,7 @@ CockroachDB is largely compatible with PostgreSQL, and can mostly be used with P - connect to your database, using Prisma ORM's [`cockroachdb` database connector](/orm/overview/databases/cockroachdb) - use [Introspection](/orm/prisma-schema/introspection) for existing projects if you already have a CockroachDB database - use [Prisma Migrate](/orm/prisma-migrate) to migrate your database schema to a new version -- use [Prisma Client](/orm/prisma-client) in your application to query your database in a type safe way based on your Prisma Schema +- use [Prisma Client](/orm/prisma-client) in your application to query your database in a type safe way based on your Prisma schema ## Differences to consider @@ -62,7 +62,7 @@ CREATE TABLE public."Post" ( ); ``` -After introspecting your database with `npx prisma db pull`, you will have a new `Post` model in your `schema.prisma` file: +After introspecting your database with `npx prisma db pull`, you will have a new `Post` model in your Prisma schema: ```prisma file=schema.prisma showLineNumbers model Post { @@ -94,7 +94,7 @@ For more information on generating database keys, see CockroachDB's [Primary key ## Example -To connect to a CockroachDB database server, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema file](/orm/prisma-schema): +To connect to a CockroachDB database server, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema](/orm/prisma-schema): ```prisma file=schema.prisma showLineNumbers datasource db { diff --git a/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx b/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx index 8c1b49686f..55ef935025 100644 --- a/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx @@ -73,7 +73,7 @@ The following is a list of community created generators. If you want to create y - [`typegraphql-prisma-nestjs`](https://github.com/EndyKaufman/typegraphql-prisma-nestjs#readme): Fork of [`typegraphql-prisma`](https://github.com/MichalLytek/typegraphql-prisma), which also generates CRUD resolvers for Prisma models but for NestJS - [`prisma-typegraphql-types-gen`](https://github.com/YassinEldeeb/prisma-tgql-types-gen): Generates [TypeGraphQL](https://typegraphql.com/) class types and enums from your prisma type definitions, the generated output can be edited without being overwritten by the next gen and has the ability to correct you when you mess up the types with your edits. - [`nexus-prisma`](https://github.com/prisma/nexus-prisma/): Allows to project Prisma models to GraphQL via [GraphQL Nexus](https://nexusjs.org/docs/) -- [`prisma-nestjs-graphql`](https://github.com/unlight/prisma-nestjs-graphql): Generates object types, inputs, args, etc. from the Prisma schema file for usage with `@nestjs/graphql` module +- [`prisma-nestjs-graphql`](https://github.com/unlight/prisma-nestjs-graphql): Generates object types, inputs, args, etc. from the Prisma schema for usage with `@nestjs/graphql` module - [`prisma-appsync`](https://github.com/maoosi/prisma-appsync): Generates a full-blown GraphQL API for [AWS AppSync](https://aws.amazon.com/appsync/) - [`prisma-kysely`](https://github.com/valtyr/prisma-kysely): Generates type definitions for Kysely, a TypeScript SQL query builder. This can be useful to perform queries against your database from an edge runtime, or to write more complex SQL queries not possible in Prisma without dropping type safety. - [`prisma-generator-nestjs-dto`](https://github.com/vegardit/prisma-generator-nestjs-dto): Generates DTO and Entity classes with relation `connect` and `create` options for use with [NestJS Resources](https://docs.nestjs.com/recipes/crud-generator) and [@nestjs/swagger](https://www.npmjs.com/package/@nestjs/swagger) diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx index d58d768f03..a6bc7ed826 100644 --- a/content/200-orm/100-prisma-schema/10-overview/index.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx @@ -1,31 +1,33 @@ --- title: 'Overview' metaTitle: 'Prisma Schema Overview' -metaDescription: 'The Prisma schema is the main configuration file when using Prisma. It is typically called schema.prisma and contains your database connection and data model.' +metaDescription: 'The Prisma schema is the main method of configuration when using Prisma. It is typically called schema.prisma and contains your database connection and data model.' --- - - -The Prisma schema file (short: _schema file_, _Prisma schema_ or _schema_) is the main configuration file for your Prisma ORM setup. It is typically called `schema.prisma` and consists of the following parts: +The Prisma schema (or _schema_ for short) is the main method of configuration for your Prisma ORM setup. It is typically a single file called `schema.prisma` and consists of the following parts: - [**Data sources**](/orm/prisma-schema/overview/data-sources): Specify the details of the data sources Prisma ORM should connect to (e.g. a PostgreSQL database) - [**Generators**](/orm/prisma-schema/overview/generators): Specifies what clients should be generated based on the data model (e.g. Prisma Client) - [**Data model definition**](/orm/prisma-schema/data-model): Specifies your application [models](/orm/prisma-schema/data-model/models#defining-models) (the shape of the data per data source) and their [relations](/orm/prisma-schema/data-model/relations) +:::note + +Looking to split your schema into multiple files? Multi-file Prisma schema is supported via the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/data-model/multiple-files) in Prisma ORM 5.15.0 and later. + +::: + See the [Prisma schema API reference](/orm/reference/prisma-schema-reference) for detailed information about each section of the schema. -Whenever a `prisma` command is invoked, the CLI typically reads some information from the schema file, e.g.: +Whenever a `prisma` command is invoked, the CLI typically reads some information from the schema, e.g.: - `prisma generate`: Reads _all_ above mentioned information from the Prisma schema to generate the correct data source client code (e.g. Prisma Client). - `prisma migrate dev`: Reads the data sources and data model definition to create a new migration. -You can also [use environment variables](#accessing-environment-variables-from-the-schema) inside the schema file to provide configuration options when a CLI command is invoked. - - +You can also [use environment variables](#accessing-environment-variables-from-the-schema) inside the schema to provide configuration options when a CLI command is invoked. ## Example -The following is an example of a Prisma schema file that specifies: +The following is an example of a Prisma schema that specifies: - A data source (PostgreSQL or MongoDB) - A generator (Prisma Client) @@ -113,17 +115,23 @@ enum Role { ## Naming -The default name for the schema file is `schema.prisma`. When your schema file is named like this, the Prisma CLI will detect it automatically in the directory where you invoke the CLI command (or any of its subdirectories). +The default name for the schema is `schema.prisma`. When your schema is named like this, the Prisma CLI will detect it automatically in the directory where you invoke the CLI command (or any of its subdirectories). -If the file is named differently, you can provide the `--schema` argument to the Prisma CLI with the path to the schema file, e.g.: +If the file is named differently, you can provide the `--schema` argument to the Prisma CLI with the path to a schema file, e.g.: ``` prisma generate --schema ./database/myschema.prisma ``` +:::note + +If you are using the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/data-model/multiple-files) any files in the `prisma/schema` directory are detected automatically. + +::: + ## Syntax -The schema file is written in Prisma Schema Language (PSL). +Prisma schema files are written in Prisma Schema Language (PSL). ### VS Code @@ -144,9 +152,9 @@ model User { ``` ```` -## Prisma schema file location +## Prisma schema location -The Prisma CLI looks for the Prisma schema file in the following locations, in the following order: +The Prisma CLI looks for the Prisma schema in the following locations, in the following order: 1. The location specified by the [`--schema` flag](/orm/reference/prisma-cli-reference), which is available when you `introspect`, `generate`, `migrate`, and `studio`: @@ -167,7 +175,7 @@ The Prisma CLI looks for the Prisma schema file in the following locations, in t - `./prisma/schema.prisma` - `./schema.prisma` -The Prisma CLI outputs the path of the schema file that will be used. The following example shows the terminal output for `prisma db pull`: +The Prisma CLI outputs the path of the schema that will be used. The following example shows the terminal output for `prisma db pull`: ```no-lines Environment variables loaded from .env @@ -185,7 +193,7 @@ Run prisma generate to generate Prisma Client. You can use environment variables to provide configuration options when a CLI command is invoked, or a Prisma Client query is run. -Hardcoding URLs directly in your schema is possible but is discouraged because it poses a security risk. Using environment variables in the schema allows you to **keep secrets out of the schema file** which in turn **improves the portability of the schema** by allowing you to use it in different environments. +Hardcoding URLs directly in your schema is possible but is discouraged because it poses a security risk. Using environment variables in the schema allows you to **keep secrets out of the schema** which in turn **improves the portability of the schema** by allowing you to use it in different environments. Environment variables can be accessed using the `env()` function: @@ -205,10 +213,10 @@ See [Environment variables](/orm/more/development-environment/environment-variab ## Comments -There are two types of comments that are supported in the schema file: +There are two types of comments that are supported in Prisma schema files: -- `// comment`: This comment is for the reader's clarity and is not present in the abstract syntax tree (AST) of the schema file. -- `/// comment`: These comments will show up in the abstract syntax tree (AST) of the schema file as descriptions to AST nodes. Tools can then use these comments to provide additional information. All comments are attached to the next available node - [free-floating comments](https://github.com/prisma/prisma/issues/3544) are not supported and are not included in the AST. +- `// comment`: This comment is for the reader's clarity and is not present in the abstract syntax tree (AST) of the schema. +- `/// comment`: These comments will show up in the abstract syntax tree (AST) of the schema as descriptions to AST nodes. Tools can then use these comments to provide additional information. All comments are attached to the next available node - [free-floating comments](https://github.com/prisma/prisma/issues/3544) are not supported and are not included in the AST. Here are some different examples: diff --git a/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx b/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx index 1be3ef9844..f512a7f8ac 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx +++ b/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx @@ -28,7 +28,7 @@ The `views` preview feature allows you to represent views in your Prisma schema ## Enable the `views` preview feature -Support for views is currently in an early preview. To enable the `views` preview feature, add the `views` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema file: +Support for views is currently in an early preview. To enable the `views` preview feature, add the `views` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: ```prisma file=schema.prisma highlight=3;add showLineNumbers generator client { diff --git a/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx b/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx index 2561116c77..5585142dfa 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx +++ b/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx @@ -15,7 +15,7 @@ Multiple database schema support is currently available with the PostgreSQL, Coc Many database providers allow you to organize database tables into named groups. You can use this to make the logical structure of the data model easier to understand, or to avoid naming collisions between tables. -In PostgreSQL, CockroachDB, and SQL Server, these groups are known as schemas. We will refer to them as _database schemas_ to distinguish them from Prisma ORM's own schema file. +In PostgreSQL, CockroachDB, and SQL Server, these groups are known as schemas. We will refer to them as _database schemas_ to distinguish them from Prisma ORM's own schema. This guide explains how to: @@ -28,7 +28,7 @@ This guide explains how to: ## How to enable the `multiSchema` preview feature -Multi-schema support is currently in preview. To enable the `multiSchema` preview feature, add the `multiSchema` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema file: +Multi-schema support is currently in preview. To enable the `multiSchema` preview feature, add the `multiSchema` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: ```prisma file=schema.prisma highlight=3;add showLineNumbers generator client { diff --git a/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx b/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx new file mode 100644 index 0000000000..1a45e5cf9a --- /dev/null +++ b/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx @@ -0,0 +1,71 @@ +--- +title: Multi-file Prisma schema +metaTitle: Prisma schema with multiple files +metaDescription: Learn how to split your Prisma schema into multiple files. +--- + +:::tip + +Multi-file Prisma schema is available via the `prismaSchemaFolder` preview feature in Prisma versions 5.15.0 and later. + +::: + +## How to enable multi-file Prisma schema support + +Multiple Prisma schema file support is currently in preview. To enable the feature, add the `prismaSchemaFolder` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: + +```prisma file=schema.prisma showLineNumbers +generator client { + provider = "prisma-client-js" + //add-next-line + previewFeatures = ["prismaSchemaFolder"] +} + +datasource db { + provider = "postgresql" + url = env("DATABASE_URL") +} +``` + +## How to include multiple Prisma schema files in your project + +To use multiple Prisma schema files, add a `schema` inside of your current `prisma` directory. With the `prismaSchemaFolder` Preview feature enabled, you can add as many files as you want to the `prisma/schema` directory. + +## How to use existing Prisma CLI commands with multiple Prisma schema files + +Existing Prisma CLI commands have been updated to support multiple Prisma files. Simply replace references to a file with a directory. As an example, the following `prisma migrate diff` command: + +```terminal +npx prisma migrate diff \ +--from-empty \ +--to-schema-datamodel prisma/schema.prisma \ +--script > prisma/migrations/0_init/migration.sql +``` + +becomes the following: + +```terminal +npx prisma migrate diff \ +--from-empty \ +//highlight-next-line +--to-schema-datamodel prisma/schema \ +--script > prisma/migrations/0_init/migration.sql +``` + +## Best practices + +We’ve found that a few best practices work well with this new feature and will help you get the most out of it: + +1. Organize your files by domain: group related models into the same file. For example, keep all user-related models in `user.prisma` while post-related models go in `post.prisma`. Try to avoid having “kitchen sink” schema files. + +1. Use clear naming conventions: schema files should be named clearly and succinctly. Use names like `user.prisma` and `post.prisma` and not `myModels.prisma` or `CommentFeaturesSchema.prisma`. + +1. Have an obvious “main” schema file: while you can now have as many schema files as you want, you’ll still need a place where you define `datasource` and `generator` blocks. We recommend having a single schema file that’s obviously the “main” file so that these blocks are easy to find. `main.prisma`, `schema.prisma`, and `base.prisma` are a few we’ve seen that work well. + +## Examples + +Our fork of [dub by dub.co](https://github.com/prisma/dub) is a great example of a real world project adapted to use multiple Prisma schema files. + +## Learn more about the `prismaSchemaFolder` preview feature + +To learn more about future plans for the `prismaSchemaFolder` preview feature, or to give feedback, refer to [our Github issue](https://github.com/prisma/prisma/issues/1122). diff --git a/content/200-orm/100-prisma-schema/50-introspection.mdx b/content/200-orm/100-prisma-schema/50-introspection.mdx index fea51a3b60..b41d630399 100644 --- a/content/200-orm/100-prisma-schema/50-introspection.mdx +++ b/content/200-orm/100-prisma-schema/50-introspection.mdx @@ -315,7 +315,7 @@ Note that you can rename the [Prisma-ORM level](/orm/prisma-schema/data-model/re ## Introspection with an existing schema -Running `prisma db pull` for relational databases with an existing schema file merges manual changes made to the schema, with changes made in the database. (This functionality has been added for the first time with version 2.6.0.) For MongoDB, Introspection for now is meant to be done only once for the initial data model. Running it repeatedly will lead to loss of custom changes, as the ones listed below. +Running `prisma db pull` for relational databases with an existing Prisma schema merges manual changes made to the schema, with changes made in the database. (This functionality has been added for the first time with version 2.6.0.) For MongoDB, Introspection for now is meant to be done only once for the initial data model. Running it repeatedly will lead to loss of custom changes, as the ones listed below. Introspection for relational databases maintains the following manual changes: @@ -339,7 +339,7 @@ The following properties of the schema are determined by the database: ### Force overwrite -To overwrite manual changes, and generate a schema based solely on the introspected database and ignore any existing schema file, add the `--force` flag to the `db pull` command: +To overwrite manual changes, and generate a schema based solely on the introspected database and ignore any existing Prisma schema, add the `--force` flag to the `db pull` command: ```terminal npx prisma db pull --force diff --git a/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx b/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx index d2e9e9985e..17c169f51f 100644 --- a/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx +++ b/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx @@ -34,7 +34,7 @@ Prisma's `postgresqlExtensions` preview feature allows you to represent PostgreS ## How to enable the `postgresqlExtensions` preview feature -Representing PostgreSQL extensions in your Prisma schema is currently a preview feature. To enable the `postgresqlExtensions` preview feature, you will need to add the `postgresqlExtensions` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema file: +Representing PostgreSQL extensions in your Prisma schema is currently a preview feature. To enable the `postgresqlExtensions` preview feature, you will need to add the `postgresqlExtensions` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: ```prisma file=schema.prisma highlight=3;add showLineNumbers generator client { diff --git a/content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx b/content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx index 78892025ad..77b2313739 100644 --- a/content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx +++ b/content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx @@ -243,7 +243,7 @@ This plugin will allow you to copy your `schema.prisma` file into your bundled c -Depending on how your application is bundled, you may need to copy the schema file to a location other than `./`. Use the `serverless package` command to package your code locally so you can review where your schema should be put. +Depending on how your application is bundled, you may need to copy the schema to a location other than `./`. Use the `serverless package` command to package your code locally so you can review where your schema should be put. @@ -289,7 +289,7 @@ custom: #### 4. Wrapping up -You can now re-package and re-deploy your application. To do so, run `serverless deploy`. Webpack output will show the schema file being moved with `copy-webpack-plugin`: +You can now re-package and re-deploy your application. To do so, run `serverless deploy`. Webpack output will show the schema being moved with `copy-webpack-plugin`: diff --git a/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/070-migration-histories.mdx b/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/070-migration-histories.mdx index 3a5f210960..3f009f5f67 100644 --- a/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/070-migration-histories.mdx +++ b/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/070-migration-histories.mdx @@ -87,4 +87,4 @@ You must commit the entire `prisma/migrations` folder to source control. This in Source-controlling the `schema.prisma` file is not enough - you must include your migration history. This is because: - As you start to [customize migrations](/orm/prisma-migrate/workflows/development-and-production#customizing-migrations), your migration history contains **information that cannot be represented in the Prisma schema**. For example, you can customize a migration to mitigate data loss that would be caused by a breaking change. -- The `prisma migrate deploy` command, which is used to deploy changes to staging, testing, and production environments, _only_ runs migration files. It does not use the Prisma schema file to fetch the models. +- The `prisma migrate deploy` command, which is used to deploy changes to staging, testing, and production environments, _only_ runs migration files. It does not use the Prisma schema to fetch the models. diff --git a/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx b/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx index 12cbaef527..05da0817fa 100644 --- a/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx +++ b/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx @@ -203,9 +203,9 @@ Your `schema.prisma` and local database now include your team's changes, and the You should commit the following files to source control: - The contents of the `.prisma/migrations` folder, including the `migration_lock.toml` file -- The Prisma schema file (`schema.prisma`) +- The Prisma schema (`schema.prisma`) Source-controlling the `schema.prisma` file is not enough - you must include your migration history. This is because: - As you start to [customize migrations](/orm/prisma-migrate/workflows/customizing-migrations), your migration history contains **information that cannot be represented in the Prisma schema**. For example, you can customize a migration to mitigate data loss that would be caused by a breaking change. -- The `prisma migrate deploy` command, which is used to deploy changes to staging, testing, and production environments, _only_ runs migration files. Prisma Migrate only uses the schema file to read the `url` and `provider` fields, not models and fields. +- The `prisma migrate deploy` command, which is used to deploy changes to staging, testing, and production environments, _only_ runs migration files. Prisma Migrate only uses the schema to read the `url` and `provider` fields, not models and fields. diff --git a/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx b/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx index 52bd3faf85..a84388c722 100644 --- a/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx +++ b/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx @@ -41,7 +41,7 @@ In earlier versions of Prisma ORM, you must instead add a SQL command to your mi ## How to install a PostgreSQL extension as part of a migration -This section describes how to add a SQL command to a migration file to activate a PostgreSQL extension. If you manage PostgreSQL extensions in your Prisma schema file with the `postgresqlExtensions` preview feature instead, see [How to migrate PostgreSQL extensions](/orm/prisma-schema/postgresql-extensions#how-to-migrate-postgresql-extensions). +This section describes how to add a SQL command to a migration file to activate a PostgreSQL extension. If you manage PostgreSQL extensions in your Prisma schema with the `postgresqlExtensions` preview feature instead, see [How to migrate PostgreSQL extensions](/orm/prisma-schema/postgresql-extensions#how-to-migrate-postgresql-extensions). The following example demonstrates how to install the `pgcrypto` extension as part of a migration: diff --git a/content/200-orm/500-reference/200-prisma-cli-reference.mdx b/content/200-orm/500-reference/200-prisma-cli-reference.mdx index bd173475dc..a32b58f5f9 100644 --- a/content/200-orm/500-reference/200-prisma-cli-reference.mdx +++ b/content/200-orm/500-reference/200-prisma-cli-reference.mdx @@ -320,7 +320,7 @@ The `generate` command is most often used to generate Prisma Client with the `pr 1. Searches the current directory and parent directories to find the applicable `npm` project. It will create a `package.json` file in the current directory if it cannot find one. 2. Installs the `@prisma/client` into the `npm` project if it is not already present. -3. Inspects the current directory to find a Prisma schema file to process. It will then generate a customized [Prisma Client](https://github.com/prisma/prisma-client-js) for your project. +3. Inspects the current directory to find a Prisma schema to process. It will then generate a customized [Prisma Client](https://github.com/prisma/prisma-client-js) for your project. #### Prerequisites @@ -850,7 +850,7 @@ model Profile { ### `db push` -The `db push` command pushes the state of your Prisma schema file to the database without using migrations. It creates the database if the database does not exist. +The `db push` command pushes the state of your Prisma schema to the database without using migrations. It creates the database if the database does not exist. This command is a good choice when you do not need to version schema changes, such as during prototyping and local development. diff --git a/content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx b/content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx index 37869a7654..27869d05a4 100644 --- a/content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx +++ b/content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx @@ -30,6 +30,7 @@ The following [Preview](/orm/more/releases#preview) feature flags are available | `relationJoins` | [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/22288) | | `nativeDistinct` | [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/22287) | | `omitApi` | [5.13.0](https://github.com/prisma/prisma/releases/tag/5.13.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/23924) | +| `prismaSchemaFolder` | [5.15.0](https://github.com/prisma/prisma/releases/tag/5.15.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/23924) | To enable a Preview feature, [add the feature flag to the `generator` block](#enabling-a-prisma-client-preview-feature) in your `schema.prisma` file. [Share your feedback on all Preview features on GitHub](https://github.com/prisma/prisma/issues/3108). diff --git a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdx b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdx index 3ecbc72dec..baeeb1e520 100644 --- a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdx +++ b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdx @@ -146,7 +146,7 @@ If you were using [native database types](/orm/reference/prisma-schema-reference 1. Backup your existing `schema.prisma` file (e.g. use version control) 2. Update your `datasource` provider from `postgresql` to `cockroachdb` -3. Use `npx prisma db pull --force` in order to overwrite your existing Prisma schema file (including native types) to those that are on your CockroachDB instance. +3. Use `npx prisma db pull --force` in order to overwrite your existing Prisma schema (including native types) to those that are on your CockroachDB instance. 4. Review changes between your Prisma schema backup and the new Prisma schema generated by `db pull`. You can either use the new schema as is, or update it to include your preferred spacing, comments, etc. 5. Delete your existing migrations. We will be [performing a baseline](/getting-started/setup-prisma/add-to-existing-project/relational-databases/baseline-your-database-typescript-cockroachdb) in order to make your local setup agree with your existing CockroachDB instance. 6. Perform the [baselining steps](/getting-started/setup-prisma/add-to-existing-project/relational-databases/baseline-your-database-typescript-cockroachdb). After these steps, you'll have migrated successfully from the `postgresql` provider to the `cockroachdb` provider! diff --git a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdx b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdx index 82a919ae29..fb32510a44 100644 --- a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdx +++ b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdx @@ -81,7 +81,7 @@ For more details, see the [Upgrading from previous versions](/orm/prisma-schema/ #### Scalar list defaults -For database connectors that support scalar lists (PostgreSQL, CockroachDB and MongoDB), Prisma ORM 4 introduces the ability to set a default value in your Prisma schema file with the `@default` attribute: +For database connectors that support scalar lists (PostgreSQL, CockroachDB and MongoDB), Prisma ORM 4 introduces the ability to set a default value in your Prisma schema with the `@default` attribute: diff --git a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdx b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdx index 3f6cf10169..56d334d6db 100644 --- a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdx +++ b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdx @@ -136,7 +136,7 @@ https://pris.ly/d/getting-started The command created a new folder called `prisma`, and two files: -- `prisma/schema.prisma`: Your Prisma schema file that specifies the [data source](/orm/prisma-schema/overview/data-sources), [generator](/orm/prisma-schema/overview/generators) and [data model](/orm/prisma-schema/data-model/models) (note that the data model doesn't exist yet, it will be generated via introspection). +- `prisma/schema.prisma`: Your Prisma schema that specifies the [data source](/orm/prisma-schema/overview/data-sources), [generator](/orm/prisma-schema/overview/generators) and [data model](/orm/prisma-schema/data-model/models) (note that the data model doesn't exist yet, it will be generated via introspection). - `.env`: A [dotenv](https://github.com/motdotla/dotenv#readme) file to configure your database [connection URL](/orm/reference/connection-urls). Your initial Prisma schema looks as follows: diff --git a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdx b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdx index dd86b69dcc..b1432185ed 100644 --- a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdx +++ b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdx @@ -135,7 +135,7 @@ https://pris.ly/d/getting-started The command created a new folder called `prisma`, and two files: -- `prisma/schema.prisma`: Your Prisma schema file that specifies the [data source](/orm/prisma-schema/overview/data-sources), [generator](/orm/prisma-schema/overview/generators) and [data model](/orm/prisma-schema/data-model/models) (note that the data model doesn't exist yet, it will be generated via introspection). +- `prisma/schema.prisma`: Your Prisma schema that specifies the [data source](/orm/prisma-schema/overview/data-sources), [generator](/orm/prisma-schema/overview/generators) and [data model](/orm/prisma-schema/data-model/models) (note that the data model doesn't exist yet, it will be generated via introspection). - `.env`: A [dotenv](https://github.com/motdotla/dotenv#readme) file to configure your database [connection URL](/orm/reference/connection-urls). Your initial Prisma schema looks as follows: diff --git a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx index b619bc2f6f..6ed1a5cd98 100644 --- a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx +++ b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx @@ -400,7 +400,7 @@ export const schema = makeSchema({ }) ``` -You can view the current version of your GraphQL schema in SDL in the generated GraphQL schema file in `./schema.graphql`. +You can view the current version of your GraphQL schema in SDL in the generated GraphQL schema in `./schema.graphql`. ## 3. Migrate GraphQL operations diff --git a/content/200-orm/800-more/450-migrating-to-prisma/01-migrate-from-typeorm.mdx b/content/200-orm/800-more/450-migrating-to-prisma/01-migrate-from-typeorm.mdx index fd9b267c5b..94893f5df5 100644 --- a/content/200-orm/800-more/450-migrating-to-prisma/01-migrate-from-typeorm.mdx +++ b/content/200-orm/800-more/450-migrating-to-prisma/01-migrate-from-typeorm.mdx @@ -260,10 +260,10 @@ npx prisma init This command created a new directory called `prisma` with the following files for you: -- `schema.prisma`: Your Prisma schema file that specifies your database connection and models +- `schema.prisma`: Your Prisma schema that specifies your database connection and models - `.env`: A [`dotenv`](https://github.com/motdotla/dotenv) to configure your database connection URL as an environment variable -The Prisma schema file currently looks as follows: +The Prisma schema currently looks as follows: ```prisma file=prisma/schema.prisma showLineNumbers // This is your Prisma schema file, diff --git a/content/200-orm/800-more/450-migrating-to-prisma/02-migrate-from-sequelize.mdx b/content/200-orm/800-more/450-migrating-to-prisma/02-migrate-from-sequelize.mdx index df91ff2be5..3de007b931 100644 --- a/content/200-orm/800-more/450-migrating-to-prisma/02-migrate-from-sequelize.mdx +++ b/content/200-orm/800-more/450-migrating-to-prisma/02-migrate-from-sequelize.mdx @@ -190,10 +190,10 @@ npx prisma init This command created a new directory called `prisma` with the following files for you: -- `schema.prisma`: Your Prisma schema file that specifies your database connection and models +- `schema.prisma`: Your Prisma schema that specifies your database connection and models - `.env`: A [`dotenv`](https://github.com/motdotla/dotenv) to configure your database connection URL as an environment variable -The Prisma schema file currently looks as follows: +The Prisma schema currently looks as follows: ```prisma file=prisma/schema.prisma showLineNumbers // This is your Prisma schema file, diff --git a/content/200-orm/800-more/450-migrating-to-prisma/03-migrate-from-mongoose.mdx b/content/200-orm/800-more/450-migrating-to-prisma/03-migrate-from-mongoose.mdx index 3188962a7f..7ea5285637 100644 --- a/content/200-orm/800-more/450-migrating-to-prisma/03-migrate-from-mongoose.mdx +++ b/content/200-orm/800-more/450-migrating-to-prisma/03-migrate-from-mongoose.mdx @@ -167,10 +167,10 @@ npx prisma init --datasource-provider mongodb This command creates: -- A new directory called `prisma` that contains a `schema.prisma` file; your Prisma schema file specifies your database connection and models +- A new directory called `prisma` that contains a `schema.prisma` file; your Prisma schema specifies your database connection and models - `.env`: A [`dotenv`](https://github.com/motdotla/dotenv) file at the root of your project (if it doesn't already exist), used to configure your database connection URL as an environment variable -The Prisma schema file currently looks as follows: +The Prisma schema currently looks as follows: ```prisma file=prisma/schema.prisma showLineNumbers // This is your Prisma schema file, diff --git a/content/200-orm/800-more/450-migrating-to-prisma/04-migrate-from-drizzle.mdx b/content/200-orm/800-more/450-migrating-to-prisma/04-migrate-from-drizzle.mdx index 8e63bd4acb..8b78db1985 100644 --- a/content/200-orm/800-more/450-migrating-to-prisma/04-migrate-from-drizzle.mdx +++ b/content/200-orm/800-more/450-migrating-to-prisma/04-migrate-from-drizzle.mdx @@ -48,7 +48,7 @@ npx prisma init This command created a new directory called `prisma` with the following files for you: -- `schema.prisma`: Your Prisma schema file that specifies your database connection and models +- `schema.prisma`: Your Prisma schema that specifies your database connection and models - `.env`: A [`dotenv`](https://github.com/motdotla/dotenv) to configure your database connection URL as an environment variable :::note @@ -57,7 +57,7 @@ you may already have a `.env` file. If so, the `prisma init` command will append ::: -The Prisma schema file currently looks as follows: +The Prisma schema currently looks as follows: ```prisma file=prisma/schema.prisma showLineNumbers // This is your Prisma schema file, diff --git a/content/200-orm/800-more/500-development-environment/050-environment-variables/040-env-files.mdx b/content/200-orm/800-more/500-development-environment/050-environment-variables/040-env-files.mdx index 17b3f82e7d..0bf334fc1f 100644 --- a/content/200-orm/800-more/500-development-environment/050-environment-variables/040-env-files.mdx +++ b/content/200-orm/800-more/500-development-environment/050-environment-variables/040-env-files.mdx @@ -31,7 +31,7 @@ We suggest to move the contents of prisma/.env to .env to consolidate your env v The following table describes where the Prisma CLI looks for the `.env` file: -| **Command** | **Schema file location** | **`.env` file locations checked, in order** | +| **Command** | **schema location** | **`.env` file locations checked, in order** | | :---------------------------------------------- | :--------------------------------------------------------------------------- | :-------------------------------------------------------- | | `prisma [command]` | `./prisma/schema.prisma` | `./.env`
`./prisma/.env` | | `prisma [command] --schema=./a/b/schema.prisma` | `./a/b/schema.prisma` | `./.env`
`./a/b/.env`
`./prisma/.env` | diff --git a/docusaurus.config.ts b/docusaurus.config.ts index fcf037a5d9..ecfd394b58 100644 --- a/docusaurus.config.ts +++ b/docusaurus.config.ts @@ -40,7 +40,7 @@ const config: Config = { "data-project-logo": "https://www.prisma.io/docs/ai_logo.png", "data-button-text": "Ask AI", "data-modal-example-questions": - "How can I setup relations in my schema file?,What is the difference between the 'migrate dev' and 'db push' commands?,Which cache strategy should I use for my query with Prisma Accelerate?,How can I subscribe to database events with Prisma Pulse?", + "How can I setup relations in my Prisma schema?,What is the difference between the 'migrate dev' and 'db push' commands?,Which cache strategy should I use for my query with Prisma Accelerate?,How can I subscribe to database events with Prisma Pulse?", "data-button-image": "https://www.prisma.io/docs/ai_button.svg", "data-button-width": "64px", "data-button-height": "64px", From 42dc2807806171d28a413d0ca2e5ba42190c090e Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Mon, 3 Jun 2024 15:38:59 -0500 Subject: [PATCH 02/18] correct highlighting syntax --- .../100-prisma-schema/10-overview/index.mdx | 2 +- .../20-relations/400-self-relations.mdx | 14 +++++----- .../20-data-model/20-relations/index.mdx | 2 +- .../100-queries/055-pagination.mdx | 26 ++++++++++++------- .../080-null-and-undefined.mdx | 16 ++++++------ .../050-prisma-client-reference.mdx | 6 +++-- .../05-upgrading-prisma-binding-to-nexus.mdx | 4 +-- 7 files changed, 40 insertions(+), 30 deletions(-) diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx index a6bc7ed826..95546a8c29 100644 --- a/content/200-orm/100-prisma-schema/10-overview/index.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx @@ -180,7 +180,7 @@ The Prisma CLI outputs the path of the schema that will be used. The following e ```no-lines Environment variables loaded from .env //highlight-next-line -|Prisma Schema loaded from prisma/schema.prisma +Prisma Schema loaded from prisma/schema.prisma Introspecting based on datasource defined in prisma/schema.prisma … diff --git a/content/200-orm/100-prisma-schema/20-data-model/20-relations/400-self-relations.mdx b/content/200-orm/100-prisma-schema/20-data-model/20-relations/400-self-relations.mdx index 885b6c9f04..b65ef7bfac 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/20-relations/400-self-relations.mdx +++ b/content/200-orm/100-prisma-schema/20-data-model/20-relations/400-self-relations.mdx @@ -78,7 +78,7 @@ model User { -```prisma highlight=4;normal +```prisma model User { id String @id @default(auto()) @map("_id") @db.ObjectId name String? @@ -97,7 +97,7 @@ Alternatively, you could rewrite this so that `predecessor` is backed by `predec -```prisma highlight=5,6;normal +```prisma model User { id Int @id @default(autoincrement()) name String? @@ -112,7 +112,7 @@ model User { -```prisma highlight=5,6;normal +```prisma model User { id String @id @default(auto()) @map("_id") @db.ObjectId name String? @@ -129,16 +129,18 @@ model User { No matter which side is backed by a foreign key, Prisma Client surfaces both the `predecessor` and `successor` fields: -```ts line-number +```ts showLineNumbers const x = await prisma.user.create({ data: { name: "Bob McBob", -| successor: { + //highlight-next-line + successor: { connect: { id: 2, }, }, -| predecessor: { + //highlight-next-line + predecessor: { connect: { id: 4, }, diff --git a/content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx b/content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx index 6425dae8c5..a859de22e0 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx +++ b/content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx @@ -180,7 +180,7 @@ const getAuthor = await prisma.user.findUnique({ }, include: { //highlight-next-line -| posts: true, // All posts where authorId == 20 + posts: true, // All posts where authorId == 20 }, }); ``` diff --git a/content/200-orm/200-prisma-client/100-queries/055-pagination.mdx b/content/200-orm/200-prisma-client/100-queries/055-pagination.mdx index d18460b664..751317c496 100644 --- a/content/200-orm/200-prisma-client/100-queries/055-pagination.mdx +++ b/content/200-orm/200-prisma-client/100-queries/055-pagination.mdx @@ -81,7 +81,7 @@ The following example returns the first 4 `Post` records that contain the word ` > **Note**: Since this is the first query, there is no cursor to pass in. -```ts line-number +```ts showLineNumbers const firstQueryResults = await prisma.post.findMany({ take: 4, where: { @@ -97,8 +97,10 @@ const firstQueryResults = await prisma.post.findMany({ // Bookmark your location in the result set - in this // case, the ID of the last post in the list of 4. -|const lastPostInResults = firstQueryResults[3] // Remember: zero-based index! :) -|const myCursor = lastPostInResults.id // Example: 29 +//highlight-start +const lastPostInResults = firstQueryResults[3] // Remember: zero-based index! :) +const myCursor = lastPostInResults.id // Example: 29 +//highlight-end ``` The following diagram shows the IDs of the first 4 results - or page 1. The cursor for the next query is **29**: @@ -111,9 +113,11 @@ The second query returns the first 4 `Post` records that contain the word `"Pris const secondQueryResults = await prisma.post.findMany({ take: 4, skip: 1, // Skip the cursor -| cursor: { -| id: myCursor, -| }, + //highlight-start + cursor: { + id: myCursor, + }, + //highlight-end where: { title: { contains: 'Prisma' /* Optional filter */, @@ -184,11 +188,13 @@ const secondQuery = await prisma.post.findMany({ cursor: { id: myCursor, }, -| where: { -| title: { -| contains: 'Prisma' /* Optional filter */, -| }, + //highlight-start + where: { + title: { + contains: 'Prisma' /* Optional filter */, + }, }, + //highlight-end orderBy: { id: 'asc', }, diff --git a/content/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdx b/content/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdx index 36164f533a..4fb1571bbb 100644 --- a/content/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdx +++ b/content/200-orm/200-prisma-client/200-special-fields-and-types/080-null-and-undefined.mdx @@ -257,10 +257,10 @@ updateUser: (parent, args, ctx: Context) => { return ctx.prisma.user.update({ where: { id: Number(args.id) }, data: { - //highlight-start -| email: args.authorEmail, // email cannot be null -| name: args.authorName // name set to null - potentially unwanted behavior - //highlight-end + //highlight-start + email: args.authorEmail, // email cannot be null + name: args.authorName // name set to null - potentially unwanted behavior + //highlight-end }, }) }, @@ -273,10 +273,10 @@ updateUser: (parent, args, ctx: Context) => { return ctx.prisma.user.update({ where: { id: Number(args.id) }, data: { - //highlight-start -| email: args.authorEmail != null ? args.authorEmail : undefined, // If null, do nothing -| name: args.authorName != null ? args.authorName : undefined // If null, do nothing - //highlight-end + //highlight-start + email: args.authorEmail != null ? args.authorEmail : undefined, // If null, do nothing + name: args.authorName != null ? args.authorName : undefined // If null, do nothing + //highlight-end }, }) }, diff --git a/content/200-orm/500-reference/050-prisma-client-reference.mdx b/content/200-orm/500-reference/050-prisma-client-reference.mdx index e50b6a7132..b3a3059ba7 100644 --- a/content/200-orm/500-reference/050-prisma-client-reference.mdx +++ b/content/200-orm/500-reference/050-prisma-client-reference.mdx @@ -2879,7 +2879,8 @@ const user = await prisma.profile.create({ data: { bio: 'Hello World', user: { -| create: { email: 'alice@prisma.io' }, + //highlight-next-line + create: { email: 'alice@prisma.io' }, }, }, }) @@ -2942,7 +2943,8 @@ const user = await prisma.user.update({ where: { email: 'alice@prisma.io' }, data: { posts: { -| create: { title: 'Hello World' }, + //highlight-next-line + create: { title: 'Hello World' }, }, }, }) diff --git a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx index 6ed1a5cd98..5cb2e1dcac 100644 --- a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx +++ b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx @@ -576,8 +576,8 @@ Although this code gives probably gives you a type error in your editor, you can ```graphql line-number type Query { -//highlight-next-line -| posts(searchString: String): [Post!]! + //highlight-next-line + posts(searchString: String): [Post!]! users(after: UserWhereUniqueInput, before: UserWhereUniqueInput, first: Int, last: Int, orderBy: Enumerable, skip: Int, where: UserWhereInput): [User!]! } ``` From e9e81759f266a4b8bd82ecf696d2c47f40f42f75 Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Mon, 3 Jun 2024 18:23:15 -0500 Subject: [PATCH 03/18] Apply suggestions from code review Co-authored-by: Jan Piotrowski --- content/200-orm/100-prisma-schema/10-overview/index.mdx | 2 +- .../100-prisma-schema/20-data-model/90-multiple-files.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx index 95546a8c29..4c2af85403 100644 --- a/content/200-orm/100-prisma-schema/10-overview/index.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx @@ -213,7 +213,7 @@ See [Environment variables](/orm/more/development-environment/environment-variab ## Comments -There are two types of comments that are supported in Prisma schema files: +There are two types of comments that are supported in Prisma Schema Language: - `// comment`: This comment is for the reader's clarity and is not present in the abstract syntax tree (AST) of the schema. - `/// comment`: These comments will show up in the abstract syntax tree (AST) of the schema as descriptions to AST nodes. Tools can then use these comments to provide additional information. All comments are attached to the next available node - [free-floating comments](https://github.com/prisma/prisma/issues/3544) are not supported and are not included in the AST. diff --git a/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx b/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx index 1a45e5cf9a..e95a5b62b8 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx +++ b/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx @@ -64,8 +64,8 @@ We’ve found that a few best practices work well with this new feature and will ## Examples -Our fork of [dub by dub.co](https://github.com/prisma/dub) is a great example of a real world project adapted to use multiple Prisma schema files. +Our fork of [`dub` by dub.co](https://github.com/prisma/dub) is a great example of a real world project adapted to use a multi-file Prisma Schema. ## Learn more about the `prismaSchemaFolder` preview feature -To learn more about future plans for the `prismaSchemaFolder` preview feature, or to give feedback, refer to [our Github issue](https://github.com/prisma/prisma/issues/1122). +To give feedback on the `prismaSchemaFolder` Preview feature, please refer to [our dedicated Github discussion](https://github.com/prisma/prisma/issues/1122). From e8a367be65393e80968f970cf656b0f5a8f3c25a Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Mon, 3 Jun 2024 18:27:55 -0500 Subject: [PATCH 04/18] capitalize correctly in some places --- .../110-relational-databases-node-mysql.mdx | 2 +- .../110-relational-databases-node-planetscale.mdx | 4 ++-- .../110-relational-databases-node-postgresql.mdx | 2 +- .../110-relational-databases-node-sqlserver.mdx | 2 +- .../110-relational-databases-typescript-cockroachdb.mdx | 2 +- .../110-relational-databases-typescript-mysql.mdx | 2 +- .../110-relational-databases-typescript-planetscale.mdx | 2 +- .../110-relational-databases-typescript-postgresql.mdx | 2 +- .../110-relational-databases-typescript-sqlserver.mdx | 2 +- .../100-start-from-scratch/120-mongodb-node-mongodb.mdx | 2 +- .../100-start-from-scratch/120-mongodb-typescript-mongodb.mdx | 2 +- .../120-mongodb/200-install-prisma-client-node-mongodb.mdx | 2 +- docusaurus.config.ts | 2 +- 13 files changed, 14 insertions(+), 14 deletions(-) diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx index a8047c5724..a8cfd698dd 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx @@ -58,7 +58,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx index 622da45074..b21e8cbe2a 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx @@ -51,7 +51,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init @@ -59,5 +59,5 @@ npx prisma init This command does two things: -- creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models +- creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma Schema with your database connection variable and schema models - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection) diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx index 553f40ea32..ccad457431 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx @@ -58,7 +58,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx index 6beb9a4e51..3f85d72687 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx @@ -61,7 +61,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx index abd608321d..15508850b6 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx @@ -64,7 +64,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx index 025e6df3a3..d33c7ed2fa 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx @@ -64,7 +64,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx index a5d2dddfb5..4a049f85f0 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx @@ -70,7 +70,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx index a0c411d96c..6e043e6d69 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx @@ -63,7 +63,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx index 11f885f70c..5fd6ea8af1 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx @@ -66,7 +66,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx index 71694ed74f..616ff0bc3e 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx @@ -58,7 +58,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx index e7bf93815c..801d2e02b1 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx @@ -63,7 +63,7 @@ You can now invoke the Prisma CLI by prefixing it with `npx`: npx prisma ``` -Next, set up your Prisma ORM project by creating your [Prisma schema](/orm/prisma-schema) file with the following command: +Next, set up your Prisma ORM project by creating your [Prisma Schema](/orm/prisma-schema) file with the following command: ```terminal copy npx prisma init diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx index 2ce3219ec9..2fc601295e 100644 --- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx +++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx @@ -18,7 +18,7 @@ To get started with Prisma Client, you need to install the `@prisma/client` pack npm install @prisma/client ``` -The install command invokes `prisma generate` for you which reads your Prisma schema and generates a version of Prisma Client that is _tailored_ to your models. +The install command invokes `prisma generate` for you which reads your Prisma Schema and generates a version of Prisma Client that is _tailored_ to your models. ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png) diff --git a/docusaurus.config.ts b/docusaurus.config.ts index ecfd394b58..47f69ff779 100644 --- a/docusaurus.config.ts +++ b/docusaurus.config.ts @@ -40,7 +40,7 @@ const config: Config = { "data-project-logo": "https://www.prisma.io/docs/ai_logo.png", "data-button-text": "Ask AI", "data-modal-example-questions": - "How can I setup relations in my Prisma schema?,What is the difference between the 'migrate dev' and 'db push' commands?,Which cache strategy should I use for my query with Prisma Accelerate?,How can I subscribe to database events with Prisma Pulse?", + "How can I setup relations in my Prisma Schema?,What is the difference between the 'migrate dev' and 'db push' commands?,Which cache strategy should I use for my query with Prisma Accelerate?,How can I subscribe to database events with Prisma Pulse?", "data-button-image": "https://www.prisma.io/docs/ai_button.svg", "data-button-width": "64px", "data-button-height": "64px", From 4a65701856b4c95e72093dd8537a5048c37bc241 Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Mon, 3 Jun 2024 21:48:43 -0500 Subject: [PATCH 05/18] PR feedback --- .../20-data-model/90-multiple-files.mdx | 21 +++++++------------ .../05-upgrading-prisma-binding-to-nexus.mdx | 2 +- 2 files changed, 8 insertions(+), 15 deletions(-) diff --git a/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx b/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx index e95a5b62b8..225fcf04ce 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx +++ b/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx @@ -6,13 +6,13 @@ metaDescription: Learn how to split your Prisma schema into multiple files. :::tip -Multi-file Prisma schema is available via the `prismaSchemaFolder` preview feature in Prisma versions 5.15.0 and later. +Multi-file Prisma Schema is available via the `prismaSchemaFolder` preview feature in Prisma versions 5.15.0 and later. ::: ## How to enable multi-file Prisma schema support -Multiple Prisma schema file support is currently in preview. To enable the feature, add the `prismaSchemaFolder` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: +Support for multiple Prisma schema files is currently in preview. To enable the feature, add the `prismaSchemaFolder` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: ```prisma file=schema.prisma showLineNumbers generator client { @@ -33,28 +33,21 @@ To use multiple Prisma schema files, add a `schema` inside of your current `pris ## How to use existing Prisma CLI commands with multiple Prisma schema files -Existing Prisma CLI commands have been updated to support multiple Prisma files. Simply replace references to a file with a directory. As an example, the following `prisma migrate diff` command: +For most Prisma CLI commands, no changes will be necessary to work with a multi-file Prisma schema. Only in the specific cases where you need to supply a schema via an option will a command need to be changed. In these cases, simply replace references to a file with a directory. As an example, the following `prisma db push` command: ```terminal -npx prisma migrate diff \ ---from-empty \ ---to-schema-datamodel prisma/schema.prisma \ ---script > prisma/migrations/0_init/migration.sql +npx prisma db push --schema custom/path/to/my/schema.prisma ``` becomes the following: ```terminal -npx prisma migrate diff \ ---from-empty \ -//highlight-next-line ---to-schema-datamodel prisma/schema \ ---script > prisma/migrations/0_init/migration.sql +npx prisma db push --schema custom/path/to/my/schema # note this is now a directory! ``` -## Best practices +## Tips for multi-file Prisma Schema -We’ve found that a few best practices work well with this new feature and will help you get the most out of it: +We’ve found that a few patterns work well with this new feature and will help you get the most out of it: 1. Organize your files by domain: group related models into the same file. For example, keep all user-related models in `user.prisma` while post-related models go in `post.prisma`. Try to avoid having “kitchen sink” schema files. diff --git a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx index 5cb2e1dcac..2aed8dc6ec 100644 --- a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx +++ b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/05-upgrading-prisma-binding-to-nexus.mdx @@ -400,7 +400,7 @@ export const schema = makeSchema({ }) ``` -You can view the current version of your GraphQL schema in SDL in the generated GraphQL schema in `./schema.graphql`. +You can view the current version of your GraphQL schema in SDL in the generated GraphQL schema file in `./schema.graphql`. ## 3. Migrate GraphQL operations From 1b7f2b4f8a4bab3f26d36baaeec7d8dfbbc6923c Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Mon, 3 Jun 2024 21:49:10 -0500 Subject: [PATCH 06/18] more PR feedback --- .../300-prisma-in-your-stack/04-is-prisma-an-orm.mdx | 2 +- content/200-orm/050-overview/500-databases/600-mongodb.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx b/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx index 393de9de00..a1229d44bd 100644 --- a/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx +++ b/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx @@ -182,7 +182,7 @@ Prisma ORM is a **next-generation ORM** that makes working with databases easy f > **Note:** Since Prisma Client is the most prominent tool, we often refer to it as simply Prisma. -The three tools use the [Prisma schema](/orm/prisma-schema) as a single source of truth for the database schema, your application's object schema, and the mapping between the two. It's defined by you and is your main way of configuring Prisma ORM. +These three tools use the [Prisma schema](/orm/prisma-schema) as a single source of truth for the database schema, your application's object schema, and the mapping between the two. It's defined by you and is your main way of configuring Prisma ORM. Prisma ORM makes you productive and confident in the software you're building with features such as _type safety_, rich auto-completion, and a natural API for fetching relations. diff --git a/content/200-orm/050-overview/500-databases/600-mongodb.mdx b/content/200-orm/050-overview/500-databases/600-mongodb.mdx index dc41f9339b..a9c927098f 100644 --- a/content/200-orm/050-overview/500-databases/600-mongodb.mdx +++ b/content/200-orm/050-overview/500-databases/600-mongodb.mdx @@ -33,7 +33,7 @@ Some aspects of using Prisma ORM with MongoDB are the same as when using Prisma - connect to your database, using the [`mongodb` database connector](/orm/overview/databases) - use [Introspection](/orm/prisma-schema/introspection) for existing projects if you already have a MongoDB database - use [`db push`](/orm/prisma-migrate/workflows/prototyping-your-schema) to push changes in your schema to the database -- use [Prisma Client](/orm/prisma-client) in your application to query your database in a type safe way based on your Prisma schema +- use [Prisma Client](/orm/prisma-client) in your application to query your database in a type safe way based on your Prisma Schema ## Differences to consider From ea33384f84a8becbcecf6ffa8ded8d2812c125dc Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Mon, 3 Jun 2024 22:12:36 -0500 Subject: [PATCH 07/18] move Schema location information to one file --- .../100-prisma-schema/10-overview/index.mdx | 53 ---------------- .../20-data-model/10-models.mdx | 2 +- .../90-multiple-files.mdx => 40-location.mdx} | 59 ++++++++++++++++-- .../prisma-schema/relations-intro.png | Bin 36481 -> 0 bytes .../img/orm}/sample-database.png | Bin 5 files changed, 55 insertions(+), 59 deletions(-) rename content/200-orm/100-prisma-schema/{20-data-model/90-multiple-files.mdx => 40-location.mdx} (60%) delete mode 100644 content/200-orm/100-prisma-schema/prisma-schema/relations-intro.png rename {content/200-orm/100-prisma-schema/prisma-schema => static/img/orm}/sample-database.png (100%) diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx index 4c2af85403..fc71cd26a7 100644 --- a/content/200-orm/100-prisma-schema/10-overview/index.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx @@ -113,22 +113,6 @@ enum Role { -## Naming - -The default name for the schema is `schema.prisma`. When your schema is named like this, the Prisma CLI will detect it automatically in the directory where you invoke the CLI command (or any of its subdirectories). - -If the file is named differently, you can provide the `--schema` argument to the Prisma CLI with the path to a schema file, e.g.: - -``` -prisma generate --schema ./database/myschema.prisma -``` - -:::note - -If you are using the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/data-model/multiple-files) any files in the `prisma/schema` directory are detected automatically. - -::: - ## Syntax Prisma schema files are written in Prisma Schema Language (PSL). @@ -152,43 +136,6 @@ model User { ``` ```` -## Prisma schema location - -The Prisma CLI looks for the Prisma schema in the following locations, in the following order: - -1. The location specified by the [`--schema` flag](/orm/reference/prisma-cli-reference), which is available when you `introspect`, `generate`, `migrate`, and `studio`: - - ```terminal - prisma generate --schema=./alternative/schema.prisma - ``` - -2. The location specified in the `package.json` file (version 2.7.0 and later): - - ```json - "prisma": { - "schema": "db/schema.prisma" - } - ``` - -3. Default locations: - - - `./prisma/schema.prisma` - - `./schema.prisma` - -The Prisma CLI outputs the path of the schema that will be used. The following example shows the terminal output for `prisma db pull`: - -```no-lines -Environment variables loaded from .env -//highlight-next-line -Prisma Schema loaded from prisma/schema.prisma - -Introspecting based on datasource defined in prisma/schema.prisma … - -✔ Introspected 4 models and wrote them into prisma/schema.prisma in 239ms - -Run prisma generate to generate Prisma Client. -``` - ## Accessing environment variables from the schema You can use environment variables to provide configuration options when a CLI command is invoked, or a Prisma Client query is run. diff --git a/content/200-orm/100-prisma-schema/20-data-model/10-models.mdx b/content/200-orm/100-prisma-schema/20-data-model/10-models.mdx index 297ca78035..bbde480a0a 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/10-models.mdx +++ b/content/200-orm/100-prisma-schema/20-data-model/10-models.mdx @@ -135,7 +135,7 @@ The data model definition is made up of: The corresponding database looks like this: -![](../prisma-schema/sample-database.png) +![](/img/orm/sample-database.png)
diff --git a/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx b/content/200-orm/100-prisma-schema/40-location.mdx similarity index 60% rename from content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx rename to content/200-orm/100-prisma-schema/40-location.mdx index 225fcf04ce..7dd4b57c86 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/90-multiple-files.mdx +++ b/content/200-orm/100-prisma-schema/40-location.mdx @@ -1,17 +1,66 @@ --- -title: Multi-file Prisma schema -metaTitle: Prisma schema with multiple files -metaDescription: Learn how to split your Prisma schema into multiple files. +title: Schema Location +metaTitle: Prisma Schema Location and Configuration +metaDescription: Documentation regarding proper location of Prisma Schema including default naming and multi-file schema. --- +## Default Prisma Schema location + +The Prisma CLI looks for the Prisma schema in the following locations, in the following order: + +1. The location specified by the [`--schema` flag](/orm/reference/prisma-cli-reference), which is available when you `introspect`, `generate`, `migrate`, and `studio`: + + ```terminal + prisma generate --schema=./alternative/schema.prisma + ``` + +2. The location specified in the `package.json` file (version 2.7.0 and later): + + ```json + "prisma": { + "schema": "db/schema.prisma" + } + ``` + +3. Default locations: + + - `./prisma/schema.prisma` + - `./schema.prisma` + +The Prisma CLI outputs the path of the schema that will be used. The following example shows the terminal output for `prisma db pull`: + +```no-lines +Environment variables loaded from .env +//highlight-next-line +Prisma Schema loaded from prisma/schema.prisma + +Introspecting based on datasource defined in prisma/schema.prisma … + +✔ Introspected 4 models and wrote them into prisma/schema.prisma in 239ms + +Run prisma generate to generate Prisma Client. +``` + +## Prisma Schema naming + +The default name for the schema is `schema.prisma`. When your schema is named like this, the Prisma CLI will detect it automatically in the directory where you invoke the CLI command (or any of its subdirectories). + +If the file is named differently, you can provide the `--schema` argument to the Prisma CLI with the path to a schema file, e.g.: + +``` +prisma generate --schema ./database/myschema.prisma +``` + +> If you are using the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/data-model/multiple-files) any files in the `prisma/schema` directory are detected automatically. + +## How to enable multi-file Prisma schema support + :::tip Multi-file Prisma Schema is available via the `prismaSchemaFolder` preview feature in Prisma versions 5.15.0 and later. ::: -## How to enable multi-file Prisma schema support - Support for multiple Prisma schema files is currently in preview. To enable the feature, add the `prismaSchemaFolder` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: ```prisma file=schema.prisma showLineNumbers diff --git a/content/200-orm/100-prisma-schema/prisma-schema/relations-intro.png b/content/200-orm/100-prisma-schema/prisma-schema/relations-intro.png deleted file mode 100644 index 47bb895580ea3e96bbbd7919d5b3ea192f9c0266..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 36481 zcmd41Wmr^E_dYyy4V^;|NGLsYHyDJ7f^?12B}huQ)EI#5D2%3 zm=NfRid<3#fs$_D(NKNphqKiwh68kdrz|OgkGD)`G%$Y-OI%l(=Qr)^tx!2z_^5-C;8@#SZikwvf$29 zKd*@~l6&F!g~P;&g`JWFQ94d6;y=bJrdDamK4BWqe& z*=Nn-aE5Z}awgJ59wJEsA2ky6;%UUoT=LGf|pR`(|Gp_(j>gt&;Yf&taNb+jw3hQ@y5Mr&f)tJw8_3SZNT+eD;PROXTjlQ3HCwY5xj_HunN=-0c|FJ$lY9rz{TsS@Jq@_KBo>^OrUJ5pXB~kS3HfYM4q}^Teyh!;QG-*1Z{$)=nCNmCz6Vq z0Fuucfk`%iqA?{YWa2W&-AD2K6g%@l9y(Fl>oH|I2w(#|e``+|hIZDo;3k%A7W2M4 zB&D;!XHNee*8JdE-MkSv#6lWnN{8!Getz&-kjK@16?rM?L%=|Qs_fHNn+h?K{j`AQjO6cmor)4W)wCiL=*Xp4| zHJ$-(O= z%&h+txN1*Ny%8?-+yC|B_*MES{7bp)4^ul#mRaeQE{TVvr{P-exzS>Iopon_Ap_767sqX!tW9T(5f0iEHv z5fz=zLDo+9z>bf{l5WXRlD+&`ZYAKPR}OJ-Svh@{!;$Gr^vHF^hyunbk!j`c6}pxr zvDgNAnSK__ftK5wS;NS*d~W0@SH=X=P@6E2;Sm-eit0SR)79-$$yT=TiWctSid#%M zFtt6v;!NbkJtg&+B_a8zXg3*b*To@1w-ACpvht(cSEwPmxl<#(bvw<9JJvxX`aqu> zHhnr%#rX7q1MZ=^Oa!^Un6NsM?OwJ)Tq!oa(XY_UCWWnvKJd=B3=11hmwy&*FCMng zex9a|KD%mAA@TdSmw zxDw5mg%RoiCZ$GA_I$aW&<}|lJx3;VOT6ii&IlAwsZb zzMz>`qamJO#&U1#NxONv1t)S=n@F9lJei09D-WJrT)4CvGnnyua~6oo@Y5CufTLLJ zD8G;OsF9^pD1t{k^v`B4NnR$%XwY)p-9!6Xh=4jz9ax6(EH~GrQFa_VYX|s|_=in( z#o@RFG;;7vGk0#KL9ehk;_&LL3kRavlz^*;Vd1`CQBmkq??uJHs}>?VS}x(ct3jR$ z!*~kGw8Pz-4-W(Tpe25MUN6M!(`L^Yx6w;vU3F_1O755o&YO#<;1C~$4!f(%_nchS z;NnrHTHfB0*)^Y>*_!l9)>Bo&7jXelMInarnY6Xp>-q@gDJSj&Y2_76{B8-HKl_5n@GzgvJtd%gl5N{$zHYEyJBX?A{^j_3)Yt5vuLxxoNxrgfN z`w%gac4;D-jleUsCl1XXCcPq}KEUkv1LXY=i~e1bMV~J)wse>^BI*n9h2F_=hcy?M z0y7>d?PTXb!9d|*yYwC5^Q&s*7FNo z*3C`S#nieK_Kld)oCUj+XQ2m&&TO(5d!1h*!A(87%|RFCEXxWax2;(zb}_>CzO=O| zT?9sC0y5SfUDd=(1m zavD@nY3*ras0K>>*YPjI4ekB8?J}>}o=0n`_kS9@H|?>>1mAl5b8_c&Ztq(DxT}Sa zSCHB_GwJ+I_x(Ghu!~`$XF^@*>2ujDT_f;aPuF&`L3pLa{GwmXo83lcyEZg3T9Gxi-) zE&nXAYL~Xj+Wng2$4i@<8^PJNF~G%Tz;> z!#srS(eVkZpAPq1pn6BQ$$rI9l_xkyzLov7B|!wK4QQ>ADG5*bNKL(^qgDVRbyg-LFwyhF`LiUw{-Yg z(gba)P)9-jZU_U31v0Z@VFl!JyOi+YLUpjCY3Ta~H&-+6e_?h3A|!`Ang2>no7yP? zHYcNm$&AF7TFcM9dCma0UZ7fpM9oz<`q$LH^gBBZWP8=QRDS_2@7^IZ;8WFd@=e)j z7WKatuH)lU!vRG~zA@*slMDy%kU6*#k}_nrw+11o=Pb_m!s12cb$pGW7f>Y2EaJY@rbGPlAuE}lQ1}(Is>WG!mBaZX3i1Bb&ZuzkFYiiVE^>9LI|Ic$GaNrI zg|rP#2_P4(^X1?L0*H)#lB4deW;wom&b7)}n9WexQ$&~~!tZm;h3n+aPzP#wqkNvh z?kYZH9c_32i)~i7#HP*1ieRPLjAo=X?>JEp8tg60PoAWmioUGaeNv63e#&9)o6Sfb~fL znx7wU*q8sz5%05%X(gBmbH=CE6$1VonG~s$4==`&l^0=ocq}aNWz+S+&+5W^d9-Xo z^H;yEud%T{LvE#f61i-P=Nj+&!Tn)Amlx{HDPTBvf&^Mxf`S|6rHm0_QlbibF?H=2jVo-DYr&Mnp4b|R_(Vt%;pNCuA19%xl zrOZ$MulZT6vEngIaA=S$g9h4eBrP=Pn@2e1&kG*#tR-eiEa1mfJ)96i<^0i4**u1! zl7jkdgFwNHpwU=CIy-p@XQ_okGR~NL8B>I{ESAgN>UmDQzKoHuL@?~cG=Z@nmiMWK z6OSAEdOM%sh8aGD!y=AykCpd>;7uebgL`xRCUV*N!?JH^_+3@4LJf&JxSuS{<}<5B z$|XKze}Y7pTVd|_C;6rDaSD^`MuWfgEfHkwB}WuZcW^4xitLnl0oyR0W$&@x(fg@l zY7IJgY&f{@bjH&#wCa4b9BLoK>kYSy0DA{F_HI$`60IHJJ_773)czNRtWwCu5z!QY zMZ4P+%F0$bIUN+5^mVRJ&vRW7ovr5uUsOG3F2`wZDaeYJd|uX@x{nwo2T1p3y&j=^ z+pIQ1buMOB`5ykL*cXpl%z$HypPOMD+xoqy3j#;t=_RWKkj7ruW)Z6j&y14&K?&23 z%f%9jmn~lIUoeFm%#HRgF|nUgfxj{iw5$}KoVxc;=rt-*?`hnR(+fMg6d7hk&W?2*j|Z!+T|5(~-Q3Q5 zX$%m5Il2aXf=3N(8VU<+WCP+p7?}D2IkfRYmL|gfdUEsY&=8Wn<(g0}M0FlQDKW-zVE&awU-21qHSlYn30;7Ee5AG5R*f2~hx8i}|B^2i%vwjb2q(*rXC$wyjv z!XY1!Ef#}9zk-dtW#!gR3rZC&DI?Uuv{<3|k?V1P-MMSw*qu+Nova13l$AcBqN+vK zGvk1HV_W;=E7wZ1q^gF-4Mrl62)n-9yZfyA^)CxbtB=Hu6dHs~bstkuh)z!w*2zmb zY4mQ69u>A<4>|Njz9@k{rKN6*Bu`@ly{%~QG@lB#x^i8LgwVmw4Gog&t%8on`qq_0 zE-K7;1&OUV!ee7^^OC{_twfG=PkyYgrYG4+n^u{f1=9meUyw#JufwUb>ufCy*pnV%sTUzsq>KTBz)2 zp0@aJuW=(^6nW}Aj=hQi|Jybs;0S5Z=mks)3HccqHlmuWlODrnbrXr?=HhzIx`$YF zqtELMof>}3ODcM#b6YL+yAtv~kTwD_vv%74oD=VtsoCnb14rL2q=U8w;9VfChv}kZ zYEfxj@y0;}Omwzj4;LcUUc(oTUyDStKP0JU*{TI%^FwUT_xLAgK}k@&XQu4u4-XKp zbg=`R6u^+)8GY8x{OkDWdI?p(FiFv0?I8gYgptD52M&5e0Au(Uvgb!Q@uF154rqQS zH2m&U(?f*OcX+ygk>;Hd2(|0Jz5Sw$*R47NY)*vk+iY}2@vHqt5!c4|^U_kkGRgb8 z`wXr|k&vxI9QIs_>UR2GLT(-|KBo)=dOF8f2iet9Qf7iMz?>H+rQd|W?^`X^M{^$f z{F=JEX%rEQeA)qWgn;;wMT~^xY`i(r>Ao7hA#X!MVxhTvj~_H?s)T`f>R-JLQI5lj zXN2ck7hA%#9n zzEc(WRu4f<7Wqwbc7*{-Y}mRP9uCI3r8Co0kJu_DRjrHsF5{0{!s8L(adAtwuz=rk zs)V?&Gnu0l9IJ?(P#SQ6|IXq=NMXC=c+U?ew%kb_{5}GC9s1?|>O%_VQPn92u$q?c z)NKMtoG3hDe{cRNQ4du^7aPM}Ow=M;N~c0mWkr%+DlInF1B94Qf%`pIb2d77BG5GP zdpF;-pqNLdP@^MxZB*pFYx*SBn@^iPoZJPe?>smGG%Vs?XD-NOCOGzXLcDg8r#3-L z!Ze)W{K(wL;1LNICDTZ$2_) z&sUn-sBQy(-Zag}F!JI>ifLobSCr0r*S@xKp!nomdalJL9en)!g%-4PIx>R^-pDP? zj7QCf{36*V7w-IaK1$=1Ef)EEdY6%N8xKSPQMlU$jJ-SlO^Ogg$F8Ge&5G|q+-cU9 z-z62cVyUaDrMSL}u6!1l#fjIY+QtRA0X~1N-=5zyvQCvCIN{A^u!JaS*R0=z7Uksb z={xw4H_sR9B7Z0JlfZa+8&&ZLxb&t+O0-l}R`eCAUp=ay5m70p2Ws{Zn%?<<1=<*Y)mS z!EJ<);tif!J%Z~XJ4BfC9xfnt&9HwyLFY%jnz&tz2ziEcJ(OFE}`nvw^p$HgN5 zrfO86xx5Te&mKHJWSELMlih-Xf!gVX^OOuwgj~%?Jg$|RoZ7lw_THfEPb_$xujsk0 z^3Vlm#3s+L1mWkO3WYyu-I?Na*ms%&Qrb~Uk?jaD0c4!o@Fa9tbm7}MumTqe)=fq# zH$<3^kUSE^YUnOfT)X`)HkM8zqf^JvMxXT!dse5%pk|!tYR|6iH5Qqb=Q~11 zf{Kt)QBu2PJSrvWq+1&*ZU`}Fkx3G|m_6q{wF!Z;SJ*IQ2s}d$6c4KY;?kJ&4 zkaycgjg2%s+MVpd6#s(rjc_o9T*hSSmqQ1evR*EDfM6sYojxh-H{b~?I8nI2e#epQ ze?6mbq+kGRa@zEYPqr6pDa2D8%?oHL+{zMB0P0owv zB^AcpZyRTYk1(=_ZoWfwOWwT`!do=trxEurYm=5j=DPDce27%8yP;-{nC@8{0as4R zUTrNz$oVn#Ij5_)6B0oT%tuPE<{da@6GK)_Pvr6WWHpJ0lc5CVVanQmy+0rtdHth*2_{b4_sGJ^t(!0kBFg2Zl+rqzOTjlab zX@X{6ntlF*nG!XbW zfWT*cbsJY18GB!6Jf0Hv6{YJ?8D*RAc~6XvshBfjSDFqUe%zVW)^gw2#O&UUgm3W8Kf2QRsE`jQIKM#5Z2Aq$I3FQy*CIcs>tDyn{^hV znH}j++FJUlwKInTCu})8+}~#`?|FgjgJp!B=hW!<>-YFka-dkVhu$Dx!NqD&*e*R17Iv{I`c6&3U?z8^v z^|6NQdJVZLH}{*}GXheWn-K!~Jp{{kRii`nO}Nda0ZPg{xXwA^7aeNr=l``pJykRd zOM7Nj=-_agMQYouhy*NIJp@?;$2mHW`EpV!8a7e8O^R0VwVOOcTue|Y=cXgwrJV2j{$Q?;x-I`u|Zphe# zSEnc6fWj(?^T!wBxuZA)_sh^ISyYtU14iDiJY{;)=Jww|YCJbSpf4A0MPqbiX!)RqKMy zAMj@iauoy=Ila2J+B`#u!zXejWP%GK7GtzS<@Js=?5^gC;o+6Q1T+x_TuBY`h2M6c z#DBYU3mpi`jFVXu*XxZ%2^w@3kCVIDJ1R&h_lXX(-iC*?!p?0EhnnM;Sd?j%1zJJ) zknn`Xmr9dplD&nXKnnCxpIdbGqcys2$+s~ zI#Ui0X#JJyp3&13o|600pf9hsu5itKKr-}`0>?O@+SFW5oG$@U=hzttNI;J(=7~Tm zfNkO|E0!5IQi3=E4i5@F><JQy2ELnTT9v>7ir z!G-h_K;}wE*=%)Bo5(01JNZTk;&{j?dmDFo`bt8UhJA;5N*cx0RrkYJoU3T<>{r-? zc*kO{zi*O%+44+R=G*o@HqW!Qk7fgeBe)|=Tj0V6nON)xtI(oWtA{>(9|RK&i9c75 zq?4b$lg;%7`P~;McjnY3h=)mvTOBa)$AfdQ?%0NKlM>QU8|tT#Pg0X~RrhreVu3CL zYVs^kH!MI*R|13SO2ReXE|Zs*L=e)~el=5XJ`c3ujJ!o{$gs=b>-&&vAgzGuq?820m3vMZ{`xj}EWZI>)VzI_)XfrWFfJ!^Ke zjApVjHksuES+Y9@$)2C_-0SND9_kKU91e^S3_5hn?8tQgXCB-Oo@FEzITqN z64`q=cMo@uOmR!`R$#?Y?>a}Q172BM;Ewyz4pV)ipyKk$roiD)NyWIalay#3xhF&0 zl;)7>xJ8v5QSlJL_kk~JNAx)B!Brzi#45*$&7k6Ge8-7GgGFEVUN4Nq_XPN>R_ zuFr}$B#&^uqpt(Sx#2H(;dE1O*P9_6aFWmpbke{{s)_BT9L4?4q=Y#&+}yhj1oE&+ zJtRNjCIaL~*uF#xk)(xzs9;pE-$a~nVhAw=^q)pe>oO7yiUj{{pasEdgdjCSY!i(z zkcQ%cpm^9u9a$8LzzIc!VH+s?p)NAC;G6fmg{vWsPkbiLsQ9%Fo7Q?BoQMf3SZb68 z6>R#>uQ2<+6L*n7IN_lP)hH#)AXB>Ua*#4=moL=X@02Yud}We-(Vb zY45nNf>c4~-U8+(V4;M#{aGkF=oV!%Rz;p%9rR&%3#C0TgaN^+yKbkF4xw`_ecLLW zLuKW%hube?uP$^`lPqmCaM`gQj0W0o85sLf4YV zE|024kAZsvZlAW7Z(3^iRiHXtG!-v}?j=6+xJkrPl!TcAme~D&mUxQ?{#M{7H28Al zE|TA>YqtHDBw<>MM2^?oEt~dIa zRGKlOi&j(1t8PF1oJfcvT{i3>eIaTT&-Xf-?8;Dl#d z9EOw!h;i!ZRn&}YgGHBg_1tHt`k&tHt}EAX&7N2eN8qUSt^qHj`A;dl6%MLeWO7#qIf}6R9AlnSr(8^o&pqmk+pRKnXLR-rsm3X!^qF zG|*M7(YtK%t*^9IYK~#{J#I-t3Smz8V2H&aY1{%gT;lI)EU>FtHJ$#GF)>;?R?0-E z1{U0Q&9ymrb|!q!wG`daM@2K$)O)x8?!{UA#Ct#YJ;~J5R$(Jd^5>#G$hGqF#R_T( zUM%L}fdlPQF^oACiSJS~<%1TG?*o3T)|-@JC3HmQm>8K*=oNQ|^5@6{3Smmf^Rh}- z-C!Ahq7QmzN{yii>gnBUN;R#xC5!?{t+$#J{;*4h3$8$tV|>@hOzs}w3|sA+kL&~- z6`l%N&K*L;tml0fT*1me?cb{F*TCMA5;C@9O%QJouksKYLBU3J(iRDhoj@=>P`mI& zSB^rB9#SQEJdiAgOt>|%cfiZttU*=rzb)Z0@vZuOTrF_V)|p`iKJ-#F}GSf!iJbZNuG! zc?+VhbzyfYQghs}Vs*8>)bZ`XJ*8m(YPqYYKC%N3IDCViULC?(*mm}EXwf+z-53Mi zgU@!QI($4)Xu+jHr9qTErqARSST2Vb@gcQqXUb~v$8}p$g+;47%a>p3y%q5$(Cz#r zye(5?Wi{?DQws!8&!53chs)L+d&gWSHLX}SGLz;dpU8xc3-43A?r@kXd}<}hZp!4A zqA`+RbEHxoUmg~)@6|Et8OlZmF>9)RfD@Vp28>(eN@jthEwi0Wq<8F6klfH1xqj96 zqWEI)q>S>MZSgbLSH+4u0;L{Qn0UM6_n0Re9NoeRlfy9==*)%7*^`7=D5j!0A2~K$ zc#i348szZ_dvQS{zGwv}saMhctF-CfloT|T75ZZPd|wdffD^v_G$+|m6DgAu^tjA& z3XQ%-nB3q}bC%Zlokv2HRwGD0`BI#kzrRs*92j+Ko}nVBAz)$I0%EO=HLa>d0Ra>M zlUH~|p@>em=!A57qg8ejli$0ib#FHA#G2&!2URpdEyV-;rG~##;i>hu9wu+JMy%K> z-($N)0bx8ZJr4OO`&1XY))nmEq_d5+Dnc6At%gG&y5PRV$qfiah+RMNe0;lX!EK3q z%};LN!A*uc?XBgzPG?6Be+narenr3e<9r|~2shsfiUV;lnEbwPkL35Uqf0AOm^4+> z^796~28%q?vneTVJ!`!$-}^nEXD$5-ylMqGR7W;)+y1Z{kXd|k@Ox{uy~)N~;qqj9 zz%nK>q0Ij>A}xKK8MfLs^(5B6b({|C=n30aCa0B;+2XfTJc+jcl+W*N zCdu1z{8)<*^Ian(RwJ|-OYSNahD)rh)IU)QI1RXHAV^%BLKhhQSf_y4qf70EaPR&u z)kpGQuPm+6yt%91+hYl_X%DZ9OgP%?*W_DAC1II_-JFrpO9VAa$K8sXS-OR^bV(p4 zm8wf;|7vrxeo)h_kJ31lS&i@^HSFcPm7~0-)s}A?x;a^yiQ`LaYFf$nbS7zF)tarx z>_2&!h)`9#u!|SbQ3*#uii}i03XR~Sg>gMF|D2SV z1dy)<9tI63G6>Y?nUA?`bveS5&FgO3bWp}et!u<+rhf6J*860|oIjb(7K`1o^vQ9b z*<7>%lL3N>mB~%D-sh>!-G>zm5%Ji)RY*aMDorZPDguM5{su!lH9@+S?APA!I z5n9m7*Q1$w_BaGEvf%#rC0{vx{w4v36=lSLlm^O?3D0co4t^hS-E$psPNf_o$HK2) zc45}@n1l!Cu-IGbT2%tvbow+KwVephYu!gJVefuC@rRph#w(a_=1ZDd^ z=l9CS_DH5@O3=DP5(u>2&EIfhwli9dFiK88ffP8o5fE^ugh-puiA zB+;h?U^bCltFr6p0J+``_bz+%6x-5N8_kkcYJImlX^W={<1 z;o*H0o$%*-5;60(wSiNT(5eDv`cYLcVzhM<7_>$oh}w3!q{c>*9I%&A9=FuzDItp2 z7ahvUHTd^uy^-nH0JFH^qc;)p-2C;Kzw}e7>>c~!icuha2$Pq+*{!Ba%gnsD2{Q*N zl0fLA0Ay(f#$tgTq4ve62U4O<)d@M_je)YA*5s88l0hBxfVoFchoz+OI!FjGE|fBW zBxC-Q#sLvEG#sJY_?OmD|CeY)*tn7TzyU`tlZAWKO^bYxEcsvL3&`4bRUWARFKSkD z-WVjyjmQ@0!h{3{5{B zU-7?Ir|Q??wgmR zF`4yKiy=duMSa(;j9G01UbMtmsfZzw;M*-VVq-flLmM|#4>}Z$TgE8sFQ<%(T|un9 zOH{uF*+Vm(m$@_JE6K|3=Nsvd&b-n-cT>e>)JYs4*~kXBsN z))Jzy;4v4eE06jnA5B7l6;7Lx8@BspzX5}4eD<9&OH^aYS4@*iKCcKLiuX55ceLT= zIgoByYhv|8%KU1Ah2P{=Pi)81f9UpfnDbE1j^CKxk`1t!)25y^Iu|;$+&KG%L-D|~>W7~b- z3Ku`&c%^xf`L=)nr9iVW-Jp}?WOdcmjRAqKgdp%iIyz~oMXq$azddzykJnPYxj2{l z>cy5UcZni=n(mDsN8!c8*M4{JSa8Dt^#j}-c!#mfxr^*Lsk+Pb_NHO$&3fB)dYv!U|-zg7v@w!vBoeRahta$J0D+IV(gq`Xx8~A>}_vFgGb) z>3-@2boVob8|AGg{&7TFSZv5w|hxH#dgId35GjwqT?ozU3Gsj-^og@-h=ZdKcQ zQ$z|GghA}tv55lwhLz#@?Y@^>d_sFAXpl49dX*YR6M{;-dYVQ8IeYKq{3K`vw|7=+ z6!A(SX&uuvdHu)y#_{7dq)i{w*#0V+)C7wne0?=q>&b_oIq{KOc}M0bHLX`jYi`|D^i0){3Mb279|nOubjQtI zYBh;ff(iCVxl(|FE;Dsjx5D_*ZtF_-?@wr3Sw>#9raq?%!=&wkfW)#_&`y5+%OU$j zuteNHGj76~@n~FUeil=t-l-&y0;2#Mj5L#*Ji8M4CT4th<1H8Cx9B=J;9b;tQ$ zh9R@+%nM}YR9v!nPF7BWDnQijq&D4Kle#{Y`IQ6oAB#IcU;-u)BS_p{=)TkUFdEzw z&pC3itw?a3hl%Nv(*^JW7;aLDdJUd*&V=%bpwY;8D_0!f@rbv3R-{@2`(=i z=WMR|Hu(uXNEZ#hQ$}K&-%_GO4Oj-5Pe==+=i$3ygv}DlEavW9X@t5GqjP*{dev3o?BMEr{?-31&{sIKP?8)m4EkZ;|7o_ z-M?B2qlQQkOdP$s3S2tz?_yjc-`+_fM}34Zq+0B$kGXgCX+1JV5^F!q{!{U@>9OCQ zW(fM7DK2)+v%U!b$g4?nlbAW}ap(|3y-w z@4NmHqo3#3D)aYAc(fFmd>u6P+riMWji$6Py%w=X`_R3IpNBOQ5HQC-1YeD zI1M(6J48o2`f!(P88Tr_lE>@Gp}qs3Ies>B5Zs$W4(CFPJnwJ zxZsVXYKvCn(>FpAb4&#u&lhQtLkMJVwoo;&y_q^TC&gA#s9?Q?E3~gSzz}njn=j}; zmQtR@nWdOKWSXW&_$?4effQ3iFh_Cb+y(ZSJ7aeaG7(9gzb0`FBN1X;0M@Jj($6#> zUz#bSs$6!j*oiuKP=Zg3ZJs>iiXMh4Fp@GVbkxLi)m1U$!|%SKnQNg+zsj zA!EsiQ3Xx1OCfS?IXyX+ca8__e}rAuFEqotaLGf9H2^!;p;FUIG&X9i&Yx&=&Csm> zoL6r2W3f{`%q~Q1WTZPfVVR-ytiBQZ{195bl3M@^2hcI#a%`kcEQ)tID>`4j)ObE-fdJ zVf4}zps#&^*8QV@_dy*MK!)&-HvVIc|5{0`*dPGqdh^bc7OP@QU+K9KE$Vt5O-1|q zm&<`dcPfHk2)|@fSL-Flt{+$o-uhL4ilyJPpdDl321R2CC{#^t^Com{s{BB~m=7=? zfKg%z=6#vt(wv=0z9~|c>{2R_O2HCyQZEpUwAvSzcC^fcfJz$x3@%p3Oi;(Y6D3zm2mA#?7UJJQm}Q z2`^e}+h8laW>~ssz9Jk>2%2BHosh8fIVGvrTI25;s6^SD>wP&^R(D%GF8fU`%{tEa z({g?_MeB@XoO3q|qOu&c3DFl^&nwQN1iZ5E;eobJZhP(+AI+K$if{Us1WyH&lVF1{ z6i)^&Y_Sx`fV1X6m>54Ld>xAZt&L1qSfBlx0}2&8@$U1|h5jYdU!Z>wpAf7Ylm{bk zX;Bj{wjov#uOL!%%`~7;n5-gU-;sU$8QDZJkd+T|w)eNpKUch}{1qDDtX!_{goLX2Qu=>Zzi1;sZ>@f~?n|SKcaW=yhh|Lvii$M z)VAV)*P5{}kc@!7z}cB(#Mno_es{9Zd4GceM#^-OD~4_&8T*5=8TBHmivcebtHmp% zo_Yix(Ow^23A)dmPjeFihY8dB``vRr$%(6jF;^=MR#(ZF%7|9G3Fo&dhgUDJ1aq#9 zL;e(YToiU(r{!N?X6P$iwO1?m!B8T;rIT$9>l9MiEH$4(tOSB7xhQ~>Zfc0NMlYRA zdu@P=jsM{fjQo$hdTA5a>3OljSz_ zyUEj82`<`A_b-)8*CHic*dT-CeU>GNSocpfG#?SuHAjv(B#^3WIb0qq?fSlzj5G4e-$n9a)4 zHBL*xue``Ee*4|O+~W+Og(FoCE#Y%0g&_YY4p8;EXqvg9NQ{18#xeWh3q@40Ru4Tn zq`JMmU+!iHlq(YCW@>9AgZ z#xDORc`;C6v18cqA8E_IILaMCJXdJYzT0{vzGr98eto`l6R1bVdR}ug za!}?J2AOyx$<$WFAeSu(+;HT_>lc4Y6{WTQyCxvVQH%$jeQ8(LwadLu0w07edEM;8 zSY*{*@_6sth8}fPwtm-l@0e_`8>tcoQl42Zt?ypOX4!AJ<_4GAs#!SJwsZPsD>V?W zV9dF6Tw{zEqlQKA<8sVTDJRH!1LC&WyH|M=`BfxAv`cq_tY%uM2t_iE-xB4^bo z1F3v5VsGK4MCUn+HnP#)VeB5aN zMA2QoM)@U|DPzHXB=Mqi`^m}IzPm|!#W&#mqWn^kE4CpaikI%^?Hzdi(P&#zTFBg8 z5n={BRGd~!#+zPqW(~lEV!h)XQeJspT=_Sbgv*2b=Sl14kCgBdJPQCri8&&|1EF3d3iaY3>h-bY@12?=QV+^2ax z=LIFBDU>r~L-o|65-xwS2O2`xR_g@ZA->3wqL@$W(e+it)Y_qX*ZNnr<%ql-v(c%< zWW%{n>|yYZ6VZ9B`ME$;dT!zcg+ptlzQj_FMq4|_LgP8p=YVh zj#Bjba_}nYa}{-YAayscCy&lk`H-;*}`Ut@w44Z6IXu>*o4K@1yU1X`^BYp zr$=S!o*=H=uKCN=s3Y3s{*hyCFnJ76{@qhGWX;|$ZwR^dxMii6-&e?>tmqb80lnaU z{?JIFk{Wz;DW|4&!ak6s@v0R;9irdh&I1G|8Fv6*fI=%VL`eduEPS$z+%)$S_87aU z=wmAB0DnU*I>oOB46@;)Eb@vdNMe6%lDewhRERqepWZOTf}L5R>Kwn;T>IyP zA2o1(=7Kxiy0a+3@cwt+C|L{-oS%K>{JS?@Pv%{>j^B*YhkvaK2(SPA1hQ&<-zSJn zcD;#NGS7}ULhI`7n`h9jBxACePvOx~=_UAL%ZiIzt_u(p+lS>drcZCA$u+A~3dBhl zo9m(xql4SVLZtjk(?shh!w_AeqfB1;s$ci>4HaLH@DD4LA~Y z_KInbD^E_?tpj+|0XW~q;)#yXw+BF&*Nn-J4{$orFd9kku>ZU*YbXWpR_(I1GvBoD z7RxQWr3LS%qdG93YjF5Xfg<3A!OhQ5d>zgGJxcVvU*+v3Ah6*V>m0!?4&9Y4r3vzI zhqfdb#sc*%hxtvCXz<%__Fa7#3Alpy+V6${w}ijxAs9>KpxhyOdWn;_1xe4|*70Sx z%>FTt)&PG?qn052IfX>pV}#h>JqR0B*E*GiZ8b@qb_xsG&U^eSR!FLj=eSOD?9m@9ySn$J5TO27w;f-413pN9T6qoB zD<`-8eU9JI1o%U_eM|1*0f_bFAw6uBa-^C2_AU5)pyzSH8Ai|(ROKr1Of4DhIb zMojH|q?SSxuO(K<>q>iUStXX{KZ#MX6mY~NJMR%5B*a?`Wted~SN)+-f*E-!)w zPb9+ntPglM-|AvDwkqg)yXBS3a|L_vzSpg0<+nJe>tFKzKh3>oTvSW5FFXnY!VpDa z1POwO2r5Go$-x0c2_iYekVHU4a+ENDfQ+Jm0t1NToRfe`8borGC^_ex-(I-)JVGwGHzAtqI3fta=iZThG(Wkj^UviL-AvA^cRE7Asfxxz`$;}O^tkW8QR-~ z!qBp)B>J~w5|azo0}o!XJ`BrP4d2-)DGj1tsg-Wv9DGfAZK+$ZWF#OU)X(yaN?X7S zIgiOqPV}>1vd#>13)|@f7I{XgJAbUj=nAx`?5+zYvlkNu8uX=P%CCN^nyH#y)W=0| zNMrPNcdFunEUhC`pWkx~fZIgj-o0gJen!|-CW9H~P%o8L&%%?^U+(!lGh03-gF0S% z!BC~9a2c`%0NW(Z0arZ6_gi*a9xY+8(W8*7YB%`@q`tG>^yTD2hgqr+2CuNt*ky`j zOjcF%^dq{~T$I#w!B+Wd@cr;;CNdeNDm6uET^=&Jw^Hjl9IsjK5s}ecE4difiFa!O z8nfJGBG}Q>C!3D{wJfjnVoBDct`j;@O=iew1X2t&0j;G~zpuWSM>To7DwrRyYz)_H zYpQJLY;1VQIu=sj=!SoAB|qZkAC?_-&9Qn-w*Tk0S#K>#DTAl3=TfUnD-a$(-Xi1( zF4G4?8;;YBWiTbA&*}x3kdtHHHTy@$1WTD!WOBqsvkQ9*?rrOO1RU3ZzJvV`hMMp2 z!6we}>0XHt7-w_Q6U-ztZXww4a+f>Nd8Ii?@BgRqvFk@sRh3VWg}g-MdTiWN%XQM8e$}KG@($^!#us zV&~exb)Hx6m2`BpwoU5Z4f5z+R$ZdHb?&J}UIk?n1^o<N8>~+mp;1}Wit1M%iYu+m(`sDPWSAPMDt7LT?U*ak>(L;yU ziMIb-cC;K=L$UI_#pYiIu@4|MK{U|xeuG~lv0z zweR#Zpy25oVZe3J0GKTd_WSTDR^@;D{_C^0h5$m?(4&^7-85{kYO-DEQdeKZ@9(>s zqn3=w27%*UrW=wA#~C!;SM3IKuBpq8OC*CW|kYk z9{{fbCu)Y6HEFuCeQ~ZH!0vjNWR&$N|NSN{`qkvjL9TMR;kNiUf;-h?IQnh;9U+L0 zuh=m&b5#QxRxs}Ga|;Tw4ikd!;!4V+l67`rHnxy7CpZr~HW-^Zy_pbpShel|jUHU> z+1U9B#zKXJv%}hPVPwHmd_t$w0fS8w!J<2gCc>n3&X(BHvurgMK)$yxjXTc}&R8qwM zxs(6~3t_z7*dTI%C+?pb0)X<+()jn+DGCkjiy_8=;R?>dAfN;cmh%e+J6utUl>>IJ=AtR*v zVIDr)r!;XIm>$_Kz1~(j`jyEpz8W{_ZNN?O`2{y8Nol+pB0z<&^8k`CQLL}P3#6! z`gGNj1kpo{G})~VrK5ulJzxWW-%KodgYi}jR(bp+3k$LA=MxI1c=37!aG^+r%HQ~|b}F)q291aXa(&6Z8On}zb*;EeWX z!(rkybC%!_^ux6qn+8ixY>FWS-x`-PTb8zaj1D%xI2e8w*E9#TMwQbfIjp|XeTX~$ zV_@eK&N6UVh zEsL8JJ&TGQA%i8gI#@f?H!vZ#@j)$&lPsxgb9X3Q#WYq6zsb5-eB+LL)V$V zoJxqZF+cC4`T+Q@I?s;}sW(Mu>5 zY_gttzV){EHtxvf{k6#41DGczd;N1p1M&hwNr9iUjG$W*o7Gn*nlo!1pFNIBrX=`r_E_=`%w7Zhd57f4c!@k^V;K}v8rgZDfHF=%;06!ChSEd=Zok12v-$|+<|z&eW@L7% zxc-6zA*{+NwtEN%{RSazh~t5zgrJ$=2MHnsXc;J60x*&!h%cuMkE~iTf>Uk>Ml61A zu08VG7(NJMb8e4Gkx? zB4>q=%HO0(5T4Yhu&=onEv|-iGSWkQB2_wSug{o{z&2PYuk*>sM=A88=Q{sX9Jq$$ z26AnBRtvU+fXf5WVG`CPx>IuVs#DyWYA^8K^<=DUJ-QwkZ#MUOlw9cbtJJQeBflE+ z8}A$Ene|S=>;@3n83L3pYvB7&YRwtF`>IlTS>6-WE>E;E*Y_QLW!(Jv;a%;<`h#DK z3lr88j%xy}$DYo1yU1hrHBaXsA6lBW#hL59V_v`FR8+YDpk#iRKN1_U?o%R`ewP8| z_QCG;eF$zcN7Lcw7eQA#*4zpRGao9AB+OM&CHG#MKC?eHKPDF?yA*K~0aNUijsWP9~>llk&nHpG^vs zeP5owDFgwVEtMMld{ZMg&u_qniUH$7jLI16%tK9Hn0q_7_5C!DZd}znHA@p8?XBszn&Sf3i5xLrzVoLSN(s9Xzf1*%>-lICXuc;;|Y9 zTk-;N)QcN8|6=q}5W~$3R>%+mp(9P?84yY(5*@XZ)9~SAf7VT$nD>-H|KZA1&cxbQ z)JjtDOi!D5rTCi`_gkK>D~rn!wYlR5m=_j~X|Di*rNRIPoT|077y}s5KU78hpla~D zYhTVxVQrHrFCJ~B0l({jbC77I>6QibO8BSkPcoqQz!kFhx*0G}TwC0zgk@#?i9vOa zJM3fW5WkavccbaRCvK@n5Q9HOGx^+46FQXyDnVhDCha8l^;0Pfu8$0NaJi4xwx$*m zkX7-yF-~7q<++FN`NQu}N=|#|I)WBqe=xDR+5rFKvtd&VSo|-l+UGBh?-UV!M)K&d z*gFNDCoE%)BUTiLL2wF~AE!UuI6%uldvkwl-p;!5W$G_(%I_j6bn(=FgysSWQs@T; zYwv#g2YBRv2vF|G{}7<<8_N@rC_Qt8fk5A^1UDfx*6gVfN`ly=LLRT@dc#x_F9S+7 zjGk;8!Y)BZZJ8N_!h+abT1Vt>6W<>I!3_bp!C)bQu&nbRK&?E0FqcN1fL}f>;$SU9 zcb@(LYhC7_K5qrWV>}EqHp5iC|9O%Msa1V%ls@w`H7F>AN-m)2i4fyokoxJe9bt`sc;|a3A1B`inIGr>TFb4(1<+l@b}@{BrGIco|H^8@yuHon=nqAC1!P z{vU4z^njKnp!2Dvq$SRJ+UP6?bh8R8^jE^pUj+rF75uk}{0}hNshZmQC(#L(CV`F( zB@QThQ$hK!8dFijul8@9&iY7gYf?wmfqQKn;{2aC7m#N?4Ow;TvH7nZ2>!uHyX;P` z77ibsQ+!&i6E46pYPx-ycvCdEeD1pI?)>D~ zm#7O4v~PZ?=8RP6xN;TW>`_R~6g~c)TB$#1pDVRL!I^nJ}J>R#e-HuDBM_H`lA^ zKio2?X$QZ<{E^ty6OhnwT#Fni;GAihaK5jt#eo`Zd%sufHov?jA@^n!DVO%qN?%ub ztlUbhI5f9;txVG7^8Ut7xv=f^m23lNE}vK^IOZSP^h`BV%Ea_z&WJOMcG%YWo;X70 z>^Nq@0p-`3YsOo$0wuo&vr+5SGxQJ-N#gO|wn3DLTW~!sj#*jhhN#@B+~a56zaD;` z%8xS>J;H>-&R@==`ktA06++fEOi9p9H1&*2=_%2fHox2$Ay7~kI+Ju1t|Pe`xFsW*1AnYbyTj^z(|$do-y>`)i!+o1sx#jRydwI~|msTz}K`dBPnh>>@fw9;9 zG&C*w{Tb(a=0O}-QY6x-5)wptGb@_k@O{wKk(<>=YqA01il0A_ap`y2 zUX5oP7JXfE@r|!J4rTf@<7n{V%-?}wJYqVr`gJ@Gbz|j)^?G=!aU8P%7Vp5JS*q47 z`&tA+G}|m`K#e>MyWg@f*HUtLElcWEUkZ>V_81a`b{qL;8GL`5M9R+X#ljDE_~%i7 z=64pp11AWnxAr-75D4hv2h4TD#mptGcJO5ew2^C!k#FZ`tl}^2Fk75dxEQm1JXoQg zC}x#Wntw5DX5^r4AawnBBW%Q_Q{ZZQ(qP?Y$5-wi`NRnu}P}yP6v6&V06Md`n-%}{NYk~$zv$mUH9`A8h^)x+5LTE z_(zWl{Q#nOOTZaS!E*A zD^6BM+^a6O)R2)sqT%i4?Ji($9IMJ8KH9Hsds6v^l2mdYo4;3h{D=3h$nSvA_YQuu zG)V5P!#~$Jeq-Ptc{d++_z|*Bl%|`x5j^jsfy`Z7AD7315t(gWHBlZ0-UdoTc{EJ& zwoxsnw!!Ja$)^58O23f${>zr*vvzz=y-6fu5*+BD35is0>BeihA}=&)OKA&-3Rj51 z_~HCi9f7;~_@sD@bXH8LcdA#9l~lRA1Re_DBUthxvyx&R~{V z*~V!iq@*$G&DI2mR9roLgTq*+KRk@A&`6D_hLNI6G-3J!?Xlz+y)?k&{0Dj@{ z)fYM2u9mIR?St?@<)JlJw*7l8cr3NS_}sDkA$=mT4|LnX{Fxi%K%{`=l^BM5fpBU7 zkC$X+<9_*T%ym|V1+|;WdXHK8Pjt$1S=QDQad&s2@(;S&^WLt6=y1Se->d+LMX;pB zG-Bbt%}2okbkWHxc6xrMqXbsRn(&JV-s|1K9b<6mbJHr-W)C6clz}W6e~hjEamV`HrQw*S7+WY}9RL2ldn%-Sa?QlOV)e$>(G+ z6*iUbq9>J+dUZC@<+y$7tBlC~-)s{(zuym?&(%4%E(hl7&!jZwBs!7>&AGhHqTHw{ z6{~@7k9m`RB&nB>-tc0uce9xnnB!m{<8CX@jPxgbHN7>TVwb1QvYlF4DlK z8QxNvRfN?IV={b{f4RKncJ1|v)nH^LHt~(cidXB9eQ($1sL|=3l=s&V*5p3MJGcqv zj>e1A-E?is>ur`pjl>OoZTaEZbN8-DJ#+XSo!O1PNzbE4>aTv8F`puWT}E>r9@;61 zMl1{_3q{jE(&xJ=ctslHJ-QLcAj(b0Df{Q1VikY)@SG`I_tU^3Y0O6D;5Ys+8C~c8 zE*i{7hIjsO$KWOvRyKAjrq~{N8!x8lxR=rA+mNiU6rBm;B^bPY6&3G5gpi@U)}oTA zKe~J><0&Xh2Tcir4~M3Ccd|o+S+Cblv-dT`g)T%1eS0ERXD?M76f2DxWKOa@J{Yp+ zTFBmiNE3T_%6<6fwp3z)aL-_cW!75z!U)2!7bok7PcGSHa$(32%jM4w&kG(90vypA z4&9YgyOq)VlDFhxR#VT+obEOrI~Z0Gk<4~|qy>+Bi`p-aYAOt4egFK+r-RWfcXVPnH9wQbKfg<6O%X^Q-$6C}=yf32719 z(R}&+XVoXV$Te!9Kp`V#@fC+i7F|V$)QGQnR}0+&PuL^_@AoltTc`eSV$9?fhmMt$ zNt`Wpg=HLcqvxYmC zvs@@(m*j^}4At5tBd_7ps(_~#YLD9zo9}g^Ctg*~_gHGITsv-i$)(YGsPFf> z-UUZ@_iS4`@8UuCXOA`unKtx_w@W$n*g%UxFsX*7bOxA_u^)I3D1-64pXu8Dy7ZPM zYg~+aEg4M!@y+3p?|)3}PG(J3{@ksd?UbW*&Lk0_O()7WvyZHnTE-kxBZRDgCcrsvB|0o25k=4w6EbU zNdf&p#clE}B18kegzj@fZ8x=$gsK_sGRwWFT znE7J+S!5&@wESb_Jv;2%xAlnB`W6khWBmtfkn%s?$}>k&K+V3woI`L?Ts@~?Yav(~ zen}YL9u&A~8S?od)i^9xtNAiu0lx~?8M>?GD2q=l6KwG=;|6UP69jKvH>^f0Id63t zjf#xex!P9vW&TbQ1uR2_PT-ZoNQcJj3Dk-=?l-X4U+Wzh)>tp|+KzSHf3-xWpu1pE zN<3EbnwC9c;pvCe5HjJk)$*SF52gUUz6DMU9wi2aalg{aKESFk-Yhwm#S}hKE=)#b~KD!`p8my zve$7$Cir|6RpJvwgy7)hT?*w0Xl}oyk`bpN8fA{b%`?QkI(tQd^s=f5*K7WnzUoUx z+SKSjZ@z~azs^*0lxk4OVW90KG^pjypg?x2Jw)O71iouI)?Fn=fYLMp7$>;;8+^Np zqHgr8E{Ry=I8CCjZ0$qG9PeWm;pG~ua%$U~I@np4(INpQOaOh3hI%WIrr9<=FvLh_3Zk1vI3isFO37Yh1FTOx`_ z2mB8*eNputUTqGrXq^In5@c3{j?hCVE#c9Ua7~e7+3nj4!fIL5HaC&U{?rJ`bZ9yy zv8>`Acs`!G662ck8-BySzm&4uOBpYJ|5N^~-Y*o-A2uX~$};M(43jkO38CdtFgDFO z^UosJHYZ13eeoveE+c9_gv1w~@Em&vl2$?buxFm87Hv63wsT)!GMK4RC&X0fTl~m@ z<1|2rZ*zT;z`JB!IWLR(&Qkj;v*m?C;+tVVrc?GxV|Xy^rQY>uD?mz~KUzNJ^`~u7 zO~Std!vyz1spXZ>z)SDh=vSVGE zM0-gPj}2iSt}(i_`PE~l4Xn=JOJ~!>@sb48XceI^>P%>Mw(DJFFEW?p!$49L^cv`& zOeQ8u75il;ZAY(*6OS+Jxcvf~ul`Jv252}Ie1a`r#R{8v;EX2QHbzU?S-*w!n;#^h z$2@zo<)yBQ=?=XwVE!7r1Q0Il)-}6bl+O&KJ!HCWyYHr5$@w@^FXR4o!TuxidU3ur zdeY$6g})*|WjLWPkw<$eAEAB;ZTUdKgLk?11A3-dv04HbW5WA?T1k(o302;^dLNSd zOXOl2*ff}YagTRycAS{*;=`Nro$fzEq|a~3^=Z|3r^XeznmZiecdTd2{g>pv8>bAI zzqES{&r-T^7ZpJ@!FjY4_#*^=DZ3Mt-hTL@b-axOSaSy%Y5I=-UM zf##y)0z^L$r3tKt*ky|V}TJSqy-$q2B9|TWohw6I%RCVT7`YW`3SdxZE zo_;i`?HA|L!KTrxyu$WqEZb?oJ^f4u6-(1i_fzT}&Q~#cPP~gv6%>u~BYo{OOHhRf zuy=Lq$m=UGMtv@qY8c7*ZQ{s(-XPTPm8&wRtxvESIYfZYc_M{*%+_T&^dvg9tRXc- z-fglGl0=A0?D$ioMiOhxz9G{b&6e@wOIAtU_9GMB)VX~w^Jh}(vZZ}?R&K$zhr#26 z;Td7O4%TMVeGPutqwJRn1$91C5Q&Xr>nd2E+kj=l0yMoZT+-T<_II`{+v8`m`Gl|% z!*fzZu!Q3iJL1|8w56eEiSuNoh!W}_5xWM~3DIgU%QwqP@yzf*+sKm3*;Shbc`d@zu0H|KfeJWy#jG{0?7bA;`)W*6;t zpXgCq+0vca6zN)Nbs(38_y~3f*Y*DG@srOx11mY(29;I!@8Zv4_*YI>)ZWDtyBi_=9#WL>439_~S9d#(q+xkA+ZCd0Lg}x^VQh$l~ z$DfdX!rg7uWs8=1U-^(EOl@D^JqM+TI2~=n(VCc$;jv*VEm!y4G?`ueWy;1Kmz=Yp zzWeF(c@&rwmQ^WlSCqw*N-v_n^HZb|kmAyP#iYLjF@M1t%?%2F0_j2Jm(IR%Kl*gF z!u;u-xSDAE!4yof0>=B6?qo65jj{k1^GqZif4xzY4E)mBY>Q9lrBG)ZH70!FDndc7 zlwL*~-__gB+_$`^a6txMNtKrJ@lNrVd}!YCsyoWv+zK5$8d0e;!^Bvt?Jc7 zt3-+@jbVBA+R7_$2@LKgb468^Mrmoyz>-)A$G&#Bt8GV54F{@PfKOED`qqi}!QykC zdY&Y6CpaNOiV$&Z-VX}1+}&=#HM1SXMxX{Wr}q*L3WdD4UPRU$xYry}nzr=_-xK2S zc;ucHy)=649H?8fo_p}wYtq}(UOV^piu+!z5bmUNddrYL$m@-GpWbz+Z0&>OxTm6; ztdM5?#VpleZqY1)qj%3K+XIz^b&>`}$}%R9dp;{Kv=mE!FI~x*&Hw#tq*YFQt*#13 z)*g8HL6KQ(s7D~Bh_9ksWbtM{NKq`4NYuGKc-&DxGPe47|Y3$J5C3YnRC7wQsa@cFm#tbi7&TJ=WZ(Vv6e?4#==-R>9Nss~yR+$Ilj$A_H4 zLMv_vTqX@@Xi#QJShW^$(8)M&lEO2eZMld;#Cj`r^;OLSYb zeF$Y?V}Jt^s# zs=?56T}`e@K2WP2+rupK_^Ri_B;~78D3-c*_toy){*CV59kHZ#){7+fec>G>;V=9` z2X%3oq<@L71&H2|JaWvkLL2cCOPz%M_QoYhD|nObf$=Z*@4tZg$;Xu_v8JP(Wb`i2 zVm-Ba;pXkC!H?JQyL*i%lTRa~aJwNlUHw9@Gw;oZP3}&`@A(Z*YjNZIb-+Pqka1$Y zWV_J%y7xHc#=_1@k?Bp{1!0}@x?sH{W!t(|Ros($U2oi?=92I3`?BJ8W&57%?A~^9 z%mUHxKH8_vB}ohl&O2*4HR&Lq?3_1b$< zl`{VTg;b}T$I>r6R>CGe|I@7bZsz8*j?E}`S^OYMlskwRahdn6p04;|vmc%G(lfo2 zJ!_|;0N*$j>|1~S&pV|>EHayRrrITjSB7R&?>?~$_Jhx3Nar!1rBM3<8Ho=3(Gaql6S}CfXBLI{3)*(r%AxeC2U%-7)=%mN{ zB=G(|@-kDYs3r%*m;9Xg_Ao^mzCIxlnc<r*46*4${{NnK7 zhJa$=NsyMP=E4b&s4(cAbWDn+nR3o*W8DNlMP*nJfR%Kh_oYyoD8xFC-=;Y)d*b? zImC@4eLD8-HBcCJcyZ_Ik)|qgRWDMs9-DQ#0sd6AmPy~lb=7P2c*CY`DDBHGdEO?= zMA8A>GeZs`Z^TpkjP(1#mr5T<^bzw3rZv$!nvDA8ONUM#Hf^Cs?zTPpy0f3{utAFC zpHEz7kzu>^jKo+5wpEA_;Xd5X8^GrlA5jzUwmfHe!$!8D&pUOg zoC}yd2#8bW=ZTswpgGfmwwr2FtfU$a_U#QVnjQ9NDUgeMjlU~h_=WNP*7Y?mH`2aK zHMG!;3TrxI6RCjLgEs(C=uiJ*Vaj;`ck_Z2Dgqn^ppWfVrB{CKyTo?ndObiHWA-%d zOL_j>^n!3^sGY{kM^{Sg!JY$knj;R(v(8___jX zYE1ljlCQOiGwWQ!czj+emy3!^bAG% z!NYv=)P$v_Ferq7DId>ukOp4psgUBr$&z*ze17kt+jHFLZ7HYY?+ZW5a=6&v-}nIW zcC7(GN7R9N(oBygag-5o^sDm?eMxWPecQy)eVH2J#Q*3?B1_VYa7VdXueIfRP-w9W ziJH8b6sE*mU}nmIIq4^h%wQG=D@JrjdDMez1m##6MTO?)0-7AgQJcNb?lD=*yfls1!6pa#DIt_@M)afw8jR+MUeSDteam!Ze0-gl zMKDhx-Za-*&W3hMB2S#(8f#n|$Xva47}Z<7`+Lx738U@AqpGE<0TQ#!*HjspED8NQ zzrF?x(D0c}6|Dnu*B^$wi=;y1WpJ6m^#F>xtAX8ZHp6&s7b9I*>uPMWB-G1jkzAlsa%((&X@R+_)SIb_OiFEJX29{>U zc#7NGu6wB`f1K8Lyw|#FoOK&5lB?Zw9)k0hD1iO?HnPG#gzxEXd9c;Fowh}k*S`@ts)5Z}um zADP74m$c1U@#Y5z)EdjW70oXm<$FFznc?UTY&yH)H@SBiB;|g6c1NXmJ9CcbNoriC zzS6Jq!sljJ@s_7vgvtjl1?!FxWbf2s2EhiKwX-x%3MVK#+U`FcmT@PjNbOT6I6$MT z)V*Tx>Q(ur`qJfsQ7y(t+U*%j<=XGBpkudnLkBiOY-=)j7aX)RO~usz?lsSS9^D~c?;Hljt6_7HN9ZS>iOi$!e+gey7@@O zL0{Qcisr-#)tbg>4N7IdJh|l?s*0;mdGfHI=gI9o8x6526<(7-pG)eGK{l!8pcx@z z&U7E9uZc~JQ(JsOw{=a?gH}NsNU;a-PPS_=YT8JHUlSs>%P#4wtMDme6SG~#G|vIg zzAkX?s5lPi5waoAsy+O~fR3J-W}Z?p#TwHYNzl9G1f5Kl-pOXeQ)P!6%UN6M_DZuM z4ZLPzXCBA`gSms25K*BZcPVFm=5X@qjdQ`%k%DO~9r=GU#x=gkry=oqqi5O4?$_(h z>mz94Ob-*@+NMebL5pDT8_z0H$JmC$COkases{brOH96rl0&N-c zr1IQCUY|IDBNjc27JvzkJL2ia_{0fy^^{f+4Ppbyq2k)!J%_?bxrV+6j#~XuwS~V2dkmS2R+GbC0u>W-{y$(M z*>xosOb#+w&^RfKekdR62&wj9ofz@f`l2DTscSDDmcgBs&XAGAFfN4|0mn0w{bi=6WBgcBN(3->NuK4)yZK9R+M%Sl>#k~*CC5^O--rldI^ zs#cCsP3D&jPqDY76s_I99BA5N*D5ms3FZPMw#I5QSlFrrWpRB;0{n|4?_7xy>n-1= zHrN{)}Wm_EKurEu8vLn$570SZd5-k+1BzcRW|08BVKX zgI*{9aW~qJPhRb&aj)HIDw{D+jKPr-I5<3HP&zR;%Dw1%%qjTf@zS74?c+)=j?Pg= zpkp^jzE(-+`8-9L-nk02hxD+D*)Z0d2iv}KKl~b-OiFcpieb~<-mhzTE!8U>lPtBJ zQGz8*q@;Mi zMjptBZrXiwP|xJS2XQ0IpQvaWUrA?3W0(iF<$bUxyOEH8hKiJ|`$@?yUA^4u!|n8x zK>GQlnQ4EPB+-BTVrybLllHF(o?1tRTV+nG`^tdOd?jv9L z6FM}E@G>`{+u5&9?#<6~2Y?;|{yratgv1+68>2c~+1cx*nq~*;kRJrrVjwZ0>y|ru zPw2cL(^VGBtU#yHRkqvJ$09aIt@8%Negda%(!IVmm#O{A(H9%_&aF54%UqA*0?o;J zHub{3mTirT*c1z2W(2#~)Ot!V=D&W`Zw0__>hm8Ls5aw4%up}+UoYxkckASngB8ei z2@&f*9kPH}Js_F~9I~L7|M9J)gKua)PgcCk=Bz>62Vz*e_hfO;lOTIY<-S_?18I?9 zCRp(poX2exeSd?X zlE(1UXiPM4uiJN@h~#FwQNZr-h1F>-N$jV}rJtA{;AF(4iSIxd11?qi#<-`>8cH@V zdu1iuZRetQ{tyc?>uu>3!}zBl2lZ^s_fYAB*<}<+vt#2eIJPTJ;>`&Bb_VSJROlPC z?Ox{KMiv=I^E>8TZO?DL+xb?*EYqe=3XMlKBxl>x(wNl7`tXb4mt{5Y8D$MIIwIKJ zP1gDd$`h;7lQhJf`Rs{KTcY?Y0v3GqP2W%uyLJ}k-PW_;AV*eI9gWnFe9sr!))Rz1 z+CRBWi0CXO^F9lEu-z!umS_Mylh&5*5O>j2(r~nY&h6G8aQrqfby_t_o!hq=^PXR( z1A?wL^p`wFngI6mdH3d9`cR09*=#(m&JG^mBzUEW*pS=d6;-v>Gd|~Jv9B7=A)H!5 zl_d@vHCJ+;6T>WDD-`zDN&W%TKJQ>|>Mo1TXOu#f?(~1kIdvCvR~$RkX4Cf3a#e5f zjH7d$J>C<+jIvJnRvxm=z0t+V6cSPx0TZ;?snpTpI{d^~w|8aKs?n*g-J!@2Gi%Xi z7KBT+y0%SF-KuCGtb$Ff=J4!W$m?s8X)Dbg2Im27etM=`68As-J53KkCrbMs-(@}C z%f!V@zoWeKmuF!nHh;1yK!Wfy=kYLb-#zb7+Ijn~FU$Em`%U=?2VV0A zZB4|!pg&^&cyA;p{+suPz#n*TFf^y$8v%)RB1A>X8;he`v<0)yf;{*<&%C2HHaTpf zsayoiwC6;)+w_KM_Ny`Bg>ku^+m;W4TR;9d1IkN*+`V6rp%09YX0IU1LE)dfPA9kg z;2XQo0HVRSO8(@cIb1aAnsU(91xkPbi83c32moa{YAHv&tCxiTH(!P8)On<=RKR&= zR7A%`8HOi%`?F&?V4t^b7RP6GpfxkUa)SaCL4uM9!7`TSF#Z8*sCAd_G`$QKQRDta zY~pFT6RY|&2=WQpSblDNtoK8&Yd-hjo8-)ZmomeL=ljnrc5V&ck-{v7E?PfvHz7#S z0_WMuEUw&Nv~Cl-TKgs?xcLe?8fIGWfRUJ4%WM+<IZ*&tY#M{CgkmI252&*VaZ;m|#K&p&h)-AriCyQ_Lc=Xm^Xcn<#T z!btnI)6yvrBRJ}!Z{StjJA9z31&DMY3t@^- zWLqYQqR28u|H6-_n?a!mB2i*d*M@{HNJd*-lY(}k(o2&raf$b(ySkMCmZ>|%gils%;!IZIB8d<<riZy$}4^OIgOe}7<9ayE3 zTQLA1|C2}9`~w%~&Q{gZ($aBZqwiE`_B%@U5JU}xea=f^j@lVNC$L;Zm9=la%Ueov ztSOOw##J|0IOr$IV2+k{1^Wem{@xP>*x2I-aAX#-rhpDw$D8)4tZ%6Ov6nVD&Ai`Q ze{qTVnvMSa6*zxO-HGTS{yMI#&q1;lge!m0z`h+}SdyL+B0f`J+-HeJh_i=08knO{ zbGp_h(#uF(N97o4|VKsZX!bpqcYL9*|&; zool)^$~&b^eTxJ(y~dln!1c{Kd^)3-|06x98W>L^px1qVDv%Hk>z^_sX8=!M@H7So zg@Hpq09z~G;U)UEBLMpbG7fDAF6s`k5%?H@!&N+S@sVfj)<2WP!C2znATsGUvPfoT z`@bdQ+7{BUfu^&Z5BhPsFBy(^d#9(92pC`AX*b4Or=3vVpXHfyJvj=OplJAhm!5c{ zy-MPqAPZWL)CYTJI0EQLrJ+zi`#Tg3iCrBT@SDgiXrT0da)r0z?%cIssD+*}VjLGd z;ryZd@|n>la2AVw#nGQ^A9|<}!Z_G%F6Gu_o}4spYZ1C+m-o8HZI>TAww$l6c|LB= zc>3nRt9?hVSvwL7{oe>R(37PR6M^c~u;@2-R)x>98}RpGus=uO&4(8el+GNDFtt*V z&?|9rVg_emp$YD6NlI|K8!hu+`ZM4@RuxBlM_x|ep)VzF{~)FT1Yd*grSPdct)GDvDCTN=ZqNuK$R8!<-pbbvz{sD1L9j*R-L7{P~VBIhN;$D2;r({ zgHL-}lom1RuvM|x(n%V&L%hn9OcTkh(ej}DhWtd*abyh8NAQl5ttIGATb4r za-i84{-Ne(sKWOMpS58p!+DGQ5Uds)6_vV>8_(36r2OX$et4(uc{q?N0P}yB>~c#n zR5QTCCv|Cz_V!OR_EELii^g1lEhX{MoB%z`my z`PZ`m?EDaZ=Gz)6=-nM&u%Q0=0BgJn##38Ib=qBj_yw8&`tUyLnGm<$@wkQJVK*KIgTo&m*kjLsmbWfxUdjvb?Up(U-ly61|>9 z0=vVyu^ZjzcrkI70;U&|L*D&7zeNJ98}R^rgWfz<|6Di>oFPvLdJYyR_zxrrZX6bc zI!DmmcM*bNl^SE!LtQlpVLsNq8^qcx+iQ!zkA^Ak&t{gdSsJdfdf%45eWUGQrBePt z%m2(e_J}Sqci)|%VC8bf>vm0tjcNlT@$!TdciY{G*MZeD^VYYe4gE$OY9$t$JH!|2 zv7VG(ZDP|~mMi6B@mrON@mq>3WUy~7;&T#f;G~RDCXoIJ)tR`*c(RcJxZoyo*1muh zy$Mxc04bEL=%ViHPcM$?oPllbvVOAua3Ve?Oo~_m$q0X+^ADAIyHG89i4nF7iY8wG wJ;KK3QmYCXuhd*xJf<~=yUr9Dc+Q|3+10qallK=n! diff --git a/content/200-orm/100-prisma-schema/prisma-schema/sample-database.png b/static/img/orm/sample-database.png similarity index 100% rename from content/200-orm/100-prisma-schema/prisma-schema/sample-database.png rename to static/img/orm/sample-database.png From 638b347f70236aa65f70a1c143f63537413d42fd Mon Sep 17 00:00:00 2001 From: Jan Piotrowski Date: Tue, 4 Jun 2024 10:05:53 +0000 Subject: [PATCH 08/18] move page and fix links --- .../04-location.mdx} | 14 ++++++++------ .../100-prisma-schema/10-overview/index.mdx | 4 ++-- 2 files changed, 10 insertions(+), 8 deletions(-) rename content/200-orm/100-prisma-schema/{40-location.mdx => 10-overview/04-location.mdx} (91%) diff --git a/content/200-orm/100-prisma-schema/40-location.mdx b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx similarity index 91% rename from content/200-orm/100-prisma-schema/40-location.mdx rename to content/200-orm/100-prisma-schema/10-overview/04-location.mdx index 7dd4b57c86..3c0a231686 100644 --- a/content/200-orm/100-prisma-schema/40-location.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx @@ -51,9 +51,11 @@ If the file is named differently, you can provide the `--schema` argument to the prisma generate --schema ./database/myschema.prisma ``` -> If you are using the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/data-model/multiple-files) any files in the `prisma/schema` directory are detected automatically. +> If you are using the [`prismaSchemaFolder` preview feature](#multi-file-prisma-schema) any files in the `prisma/schema` directory are detected automatically. -## How to enable multi-file Prisma schema support +## Multi-file Prisma Schema + +### How to enable multi-file Prisma schema support :::tip @@ -76,7 +78,7 @@ datasource db { } ``` -## How to include multiple Prisma schema files in your project +### How to include multiple Prisma schema files in your project To use multiple Prisma schema files, add a `schema` inside of your current `prisma` directory. With the `prismaSchemaFolder` Preview feature enabled, you can add as many files as you want to the `prisma/schema` directory. @@ -94,7 +96,7 @@ becomes the following: npx prisma db push --schema custom/path/to/my/schema # note this is now a directory! ``` -## Tips for multi-file Prisma Schema +### Tips for multi-file Prisma Schema We’ve found that a few patterns work well with this new feature and will help you get the most out of it: @@ -104,10 +106,10 @@ We’ve found that a few patterns work well with this new feature and will help 1. Have an obvious “main” schema file: while you can now have as many schema files as you want, you’ll still need a place where you define `datasource` and `generator` blocks. We recommend having a single schema file that’s obviously the “main” file so that these blocks are easy to find. `main.prisma`, `schema.prisma`, and `base.prisma` are a few we’ve seen that work well. -## Examples +### Examples Our fork of [`dub` by dub.co](https://github.com/prisma/dub) is a great example of a real world project adapted to use a multi-file Prisma Schema. -## Learn more about the `prismaSchemaFolder` preview feature +### Learn more about the `prismaSchemaFolder` preview feature To give feedback on the `prismaSchemaFolder` Preview feature, please refer to [our dedicated Github discussion](https://github.com/prisma/prisma/issues/1122). diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx index fc71cd26a7..6a1ae7a832 100644 --- a/content/200-orm/100-prisma-schema/10-overview/index.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx @@ -4,7 +4,7 @@ metaTitle: 'Prisma Schema Overview' metaDescription: 'The Prisma schema is the main method of configuration when using Prisma. It is typically called schema.prisma and contains your database connection and data model.' --- -The Prisma schema (or _schema_ for short) is the main method of configuration for your Prisma ORM setup. It is typically a single file called `schema.prisma` and consists of the following parts: +The Prisma schema (or _schema_ for short) is the main method of configuration for your Prisma ORM setup. It is typically a single file called `schema.prisma` (or multiple files with `.prisma` file extension) and consists of the following parts: - [**Data sources**](/orm/prisma-schema/overview/data-sources): Specify the details of the data sources Prisma ORM should connect to (e.g. a PostgreSQL database) - [**Generators**](/orm/prisma-schema/overview/generators): Specifies what clients should be generated based on the data model (e.g. Prisma Client) @@ -12,7 +12,7 @@ The Prisma schema (or _schema_ for short) is the main method of configuration fo :::note -Looking to split your schema into multiple files? Multi-file Prisma schema is supported via the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/data-model/multiple-files) in Prisma ORM 5.15.0 and later. +Looking to split your schema into multiple files? Multi-file Prisma schema is supported via the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/data-model/location#multi-file-prisma-schema) in Prisma ORM 5.15.0 and later. ::: From 58fedcd074aec44e2d55e7de1278ae16b9f352d2 Mon Sep 17 00:00:00 2001 From: Jan Piotrowski Date: Tue, 4 Jun 2024 10:10:23 +0000 Subject: [PATCH 09/18] fix link --- content/200-orm/100-prisma-schema/10-overview/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx index 6a1ae7a832..f9b115999d 100644 --- a/content/200-orm/100-prisma-schema/10-overview/index.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx @@ -12,7 +12,7 @@ The Prisma schema (or _schema_ for short) is the main method of configuration fo :::note -Looking to split your schema into multiple files? Multi-file Prisma schema is supported via the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/data-model/location#multi-file-prisma-schema) in Prisma ORM 5.15.0 and later. +Looking to split your schema into multiple files? Multi-file Prisma schema is supported via the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/overview/location#multi-file-prisma-schema) in Prisma ORM 5.15.0 and later. ::: From 3a90f93ea521de00d8751673351a5442831a99ff Mon Sep 17 00:00:00 2001 From: Jan Piotrowski Date: Tue, 4 Jun 2024 10:21:57 +0000 Subject: [PATCH 10/18] Restructure Location page a bit --- .../10-overview/04-location.mdx | 30 +++++++------------ .../100-prisma-schema/10-overview/index.mdx | 6 ++-- 2 files changed, 14 insertions(+), 22 deletions(-) diff --git a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx index 3c0a231686..4aaca720b5 100644 --- a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx @@ -4,7 +4,11 @@ metaTitle: Prisma Schema Location and Configuration metaDescription: Documentation regarding proper location of Prisma Schema including default naming and multi-file schema. --- -## Default Prisma Schema location +The default name for the Prisma schema is a single file `schema.prisma` in your `prisma` folder. When your schema is named like this, the Prisma CLI will detect it automatically. + +> If you are using the [`prismaSchemaFolder` preview feature](#multi-file-prisma-schema) any files in the `prisma/schema` directory are detected automatically. + +## Prisma Schema location The Prisma CLI looks for the Prisma schema in the following locations, in the following order: @@ -41,28 +45,18 @@ Introspecting based on datasource defined in prisma/schema.prisma … Run prisma generate to generate Prisma Client. ``` -## Prisma Schema naming - -The default name for the schema is `schema.prisma`. When your schema is named like this, the Prisma CLI will detect it automatically in the directory where you invoke the CLI command (or any of its subdirectories). - -If the file is named differently, you can provide the `--schema` argument to the Prisma CLI with the path to a schema file, e.g.: - -``` -prisma generate --schema ./database/myschema.prisma -``` - -> If you are using the [`prismaSchemaFolder` preview feature](#multi-file-prisma-schema) any files in the `prisma/schema` directory are detected automatically. - ## Multi-file Prisma Schema -### How to enable multi-file Prisma schema support - :::tip Multi-file Prisma Schema is available via the `prismaSchemaFolder` preview feature in Prisma versions 5.15.0 and later. ::: +To use multiple Prisma schema files, add a `schema` folder inside of your current `prisma` directory. With the `prismaSchemaFolder` Preview feature enabled, you can add as many files as you want to the `prisma/schema` directory. + +### How to enable multi-file Prisma schema support + Support for multiple Prisma schema files is currently in preview. To enable the feature, add the `prismaSchemaFolder` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: ```prisma file=schema.prisma showLineNumbers @@ -78,11 +72,7 @@ datasource db { } ``` -### How to include multiple Prisma schema files in your project - -To use multiple Prisma schema files, add a `schema` inside of your current `prisma` directory. With the `prismaSchemaFolder` Preview feature enabled, you can add as many files as you want to the `prisma/schema` directory. - -## How to use existing Prisma CLI commands with multiple Prisma schema files +### How to use existing Prisma CLI commands with multiple Prisma schema files For most Prisma CLI commands, no changes will be necessary to work with a multi-file Prisma schema. Only in the specific cases where you need to supply a schema via an option will a command need to be changed. In these cases, simply replace references to a file with a directory. As an example, the following `prisma db push` command: diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx index f9b115999d..b4e07c6ff3 100644 --- a/content/200-orm/100-prisma-schema/10-overview/index.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx @@ -4,12 +4,14 @@ metaTitle: 'Prisma Schema Overview' metaDescription: 'The Prisma schema is the main method of configuration when using Prisma. It is typically called schema.prisma and contains your database connection and data model.' --- -The Prisma schema (or _schema_ for short) is the main method of configuration for your Prisma ORM setup. It is typically a single file called `schema.prisma` (or multiple files with `.prisma` file extension) and consists of the following parts: +The Prisma schema (or _schema_ for short) is the main method of configuration for your Prisma ORM setup. It consists of the following parts: - [**Data sources**](/orm/prisma-schema/overview/data-sources): Specify the details of the data sources Prisma ORM should connect to (e.g. a PostgreSQL database) - [**Generators**](/orm/prisma-schema/overview/generators): Specifies what clients should be generated based on the data model (e.g. Prisma Client) - [**Data model definition**](/orm/prisma-schema/data-model): Specifies your application [models](/orm/prisma-schema/data-model/models#defining-models) (the shape of the data per data source) and their [relations](/orm/prisma-schema/data-model/relations) +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](/orm/prisma-schema/overview/location). + :::note Looking to split your schema into multiple files? Multi-file Prisma schema is supported via the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/overview/location#multi-file-prisma-schema) in Prisma ORM 5.15.0 and later. @@ -115,7 +117,7 @@ enum Role { ## Syntax -Prisma schema files are written in Prisma Schema Language (PSL). +Prisma schema files are written in Prisma Schema Language (PSL). See the [**Data sources**](/orm/prisma-schema/overview/data-sources), [**Generators**](/orm/prisma-schema/overview/generators) and [**Data model definition**](/orm/prisma-schema/data-model) pages for details and examples. ### VS Code From af6372464e5b073398813d8deb5cd726b6c480e6 Mon Sep 17 00:00:00 2001 From: Jan Piotrowski Date: Tue, 4 Jun 2024 12:30:22 +0200 Subject: [PATCH 11/18] Apply suggestions from code review --- content/200-orm/050-overview/500-databases/600-mongodb.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/200-orm/050-overview/500-databases/600-mongodb.mdx b/content/200-orm/050-overview/500-databases/600-mongodb.mdx index a9c927098f..44dd55c87b 100644 --- a/content/200-orm/050-overview/500-databases/600-mongodb.mdx +++ b/content/200-orm/050-overview/500-databases/600-mongodb.mdx @@ -127,7 +127,7 @@ As an example, take a MongoDB database with two collections, `User` and `Post`. - `title` field with a type of `string` - `userId` with a type of `objectID` -On introspection with `db pull`, this is pulled in to the Prisma schema as follows: +On introspection with `db pull`, this is pulled in to the Prisma Schema as follows: ```prisma file=prisma/schema.prisma showLineNumbers model Post { @@ -356,7 +356,7 @@ For more information on how to set up and manage a MongoDB database, see the [Pr ## Example -To connect to a MongoDB server, configure the [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema](/orm/prisma-schema): +To connect to a MongoDB server, configure the [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma Schema](/orm/prisma-schema): ```prisma file=schema.prisma showLineNumbers datasource db { From 98aecea67ceac796bd8390633c959bf508b3fd7a Mon Sep 17 00:00:00 2001 From: Jan Piotrowski Date: Tue, 4 Jun 2024 10:35:08 +0000 Subject: [PATCH 12/18] syntax fix --- content/200-orm/100-prisma-schema/10-overview/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx index b4e07c6ff3..3c8ed75993 100644 --- a/content/200-orm/100-prisma-schema/10-overview/index.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx @@ -117,7 +117,7 @@ enum Role { ## Syntax -Prisma schema files are written in Prisma Schema Language (PSL). See the [**Data sources**](/orm/prisma-schema/overview/data-sources), [**Generators**](/orm/prisma-schema/overview/generators) and [**Data model definition**](/orm/prisma-schema/data-model) pages for details and examples. +Prisma schema files are written in Prisma Schema Language (PSL). See the [data sources](/orm/prisma-schema/overview/data-sources), [generators](/orm/prisma-schema/overview/generators), [data model definition**](/orm/prisma-schema/data-model) and of course [Prisma schema API reference](/orm/reference/prisma-schema-reference) pages for details and examples. ### VS Code From 5bf835296fd128c32bcc4c32991d9a45d6503d23 Mon Sep 17 00:00:00 2001 From: Jan Piotrowski Date: Tue, 4 Jun 2024 10:40:28 +0000 Subject: [PATCH 13/18] change captialization --- content/200-orm/100-prisma-schema/10-overview/04-location.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx index 4aaca720b5..bcfb536ab7 100644 --- a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx @@ -1,5 +1,5 @@ --- -title: Schema Location +title: Schema location metaTitle: Prisma Schema Location and Configuration metaDescription: Documentation regarding proper location of Prisma Schema including default naming and multi-file schema. --- From 8d23a76197679ab05a65e4843cc0710b13207b44 Mon Sep 17 00:00:00 2001 From: Jan Piotrowski Date: Tue, 4 Jun 2024 12:57:55 +0200 Subject: [PATCH 14/18] Apply suggestions from code review --- content/200-orm/100-prisma-schema/10-overview/04-location.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx index bcfb536ab7..97e13987df 100644 --- a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx @@ -1,7 +1,7 @@ --- title: Schema location metaTitle: Prisma Schema Location and Configuration -metaDescription: Documentation regarding proper location of Prisma Schema including default naming and multi-file schema. +metaDescription: Documentation regarding proper location of Prisma Schema including default naming and multiple files. --- The default name for the Prisma schema is a single file `schema.prisma` in your `prisma` folder. When your schema is named like this, the Prisma CLI will detect it automatically. @@ -88,7 +88,7 @@ npx prisma db push --schema custom/path/to/my/schema # note this is now a direc ### Tips for multi-file Prisma Schema -We’ve found that a few patterns work well with this new feature and will help you get the most out of it: +We’ve found that a few patterns work well with this feature and will help you get the most out of it: 1. Organize your files by domain: group related models into the same file. For example, keep all user-related models in `user.prisma` while post-related models go in `post.prisma`. Try to avoid having “kitchen sink” schema files. From 76cd56286caa7ee8d9c476c23cd7718ea30bb432 Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Tue, 4 Jun 2024 06:32:13 -0500 Subject: [PATCH 15/18] Update content/200-orm/100-prisma-schema/10-overview/04-location.mdx --- .../200-orm/100-prisma-schema/10-overview/04-location.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx index 97e13987df..fc987f7a00 100644 --- a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx @@ -90,11 +90,11 @@ npx prisma db push --schema custom/path/to/my/schema # note this is now a direc We’ve found that a few patterns work well with this feature and will help you get the most out of it: -1. Organize your files by domain: group related models into the same file. For example, keep all user-related models in `user.prisma` while post-related models go in `post.prisma`. Try to avoid having “kitchen sink” schema files. +* Organize your files by domain: group related models into the same file. For example, keep all user-related models in `user.prisma` while post-related models go in `post.prisma`. Try to avoid having “kitchen sink” schema files. -1. Use clear naming conventions: schema files should be named clearly and succinctly. Use names like `user.prisma` and `post.prisma` and not `myModels.prisma` or `CommentFeaturesSchema.prisma`. +* Use clear naming conventions: schema files should be named clearly and succinctly. Use names like `user.prisma` and `post.prisma` and not `myModels.prisma` or `CommentFeaturesSchema.prisma`. -1. Have an obvious “main” schema file: while you can now have as many schema files as you want, you’ll still need a place where you define `datasource` and `generator` blocks. We recommend having a single schema file that’s obviously the “main” file so that these blocks are easy to find. `main.prisma`, `schema.prisma`, and `base.prisma` are a few we’ve seen that work well. +* Have an obvious “main” schema file: while you can now have as many schema files as you want, you’ll still need a place where you define `datasource` and `generator` blocks. We recommend having a single schema file that’s obviously the “main” file so that these blocks are easy to find. `main.prisma`, `schema.prisma`, and `base.prisma` are a few we’ve seen that work well. ### Examples From c5c85de417345327c52f5963807d9a23642f45ce Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Tue, 4 Jun 2024 07:18:03 -0500 Subject: [PATCH 16/18] Update content/200-orm/100-prisma-schema/10-overview/04-location.mdx --- .../100-prisma-schema/10-overview/04-location.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx index fc987f7a00..0d9e8b85e6 100644 --- a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx @@ -54,6 +54,16 @@ Multi-file Prisma Schema is available via the `prismaSchemaFolder` preview featu ::: To use multiple Prisma schema files, add a `schema` folder inside of your current `prisma` directory. With the `prismaSchemaFolder` Preview feature enabled, you can add as many files as you want to the `prisma/schema` directory. +``` +my-app/ +├─ ... +├─ prisma/ +│ ├─ schema/ +│ │ ├─ post.prisma +│ │ ├─ schema.prisma +│ │ ├─ user.prisma +├─ ... +``` ### How to enable multi-file Prisma schema support From bc87bb34b14835afce2aa5e3022d55a37e384a6d Mon Sep 17 00:00:00 2001 From: Jon Harrell <4829245+jharrell@users.noreply.github.com> Date: Tue, 4 Jun 2024 08:15:09 -0500 Subject: [PATCH 17/18] Apply suggestions from code review --- .../050-overview/500-databases/840-cockroachdb.mdx | 4 ++-- .../100-prisma-schema/10-overview/03-generators.mdx | 2 +- .../200-orm/100-prisma-schema/10-overview/04-location.mdx | 8 ++++---- content/200-orm/100-prisma-schema/10-overview/index.mdx | 8 ++++---- .../200-orm/100-prisma-schema/20-data-model/40-views.mdx | 2 +- .../100-prisma-schema/20-data-model/60-multi-schema.mdx | 2 +- content/200-orm/100-prisma-schema/50-introspection.mdx | 4 ++-- .../100-prisma-schema/80-postgresql-extensions.mdx | 2 +- .../300-workflows/100-team-development.mdx | 2 +- .../300-workflows/120-native-database-functions.mdx | 2 +- .../200-orm/500-reference/200-prisma-cli-reference.mdx | 2 +- .../500-preview-features/050-client-preview-features.mdx | 2 +- 12 files changed, 20 insertions(+), 20 deletions(-) diff --git a/content/200-orm/050-overview/500-databases/840-cockroachdb.mdx b/content/200-orm/050-overview/500-databases/840-cockroachdb.mdx index 1d6b8e203c..076112be0d 100644 --- a/content/200-orm/050-overview/500-databases/840-cockroachdb.mdx +++ b/content/200-orm/050-overview/500-databases/840-cockroachdb.mdx @@ -33,7 +33,7 @@ CockroachDB is largely compatible with PostgreSQL, and can mostly be used with P - connect to your database, using Prisma ORM's [`cockroachdb` database connector](/orm/overview/databases/cockroachdb) - use [Introspection](/orm/prisma-schema/introspection) for existing projects if you already have a CockroachDB database - use [Prisma Migrate](/orm/prisma-migrate) to migrate your database schema to a new version -- use [Prisma Client](/orm/prisma-client) in your application to query your database in a type safe way based on your Prisma schema +- use [Prisma Client](/orm/prisma-client) in your application to query your database in a type safe way based on your Prisma Schema ## Differences to consider @@ -62,7 +62,7 @@ CREATE TABLE public."Post" ( ); ``` -After introspecting your database with `npx prisma db pull`, you will have a new `Post` model in your Prisma schema: +After introspecting your database with `npx prisma db pull`, you will have a new `Post` model in your Prisma Schema: ```prisma file=schema.prisma showLineNumbers model Post { diff --git a/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx b/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx index 55ef935025..878ea626e5 100644 --- a/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/03-generators.mdx @@ -73,7 +73,7 @@ The following is a list of community created generators. If you want to create y - [`typegraphql-prisma-nestjs`](https://github.com/EndyKaufman/typegraphql-prisma-nestjs#readme): Fork of [`typegraphql-prisma`](https://github.com/MichalLytek/typegraphql-prisma), which also generates CRUD resolvers for Prisma models but for NestJS - [`prisma-typegraphql-types-gen`](https://github.com/YassinEldeeb/prisma-tgql-types-gen): Generates [TypeGraphQL](https://typegraphql.com/) class types and enums from your prisma type definitions, the generated output can be edited without being overwritten by the next gen and has the ability to correct you when you mess up the types with your edits. - [`nexus-prisma`](https://github.com/prisma/nexus-prisma/): Allows to project Prisma models to GraphQL via [GraphQL Nexus](https://nexusjs.org/docs/) -- [`prisma-nestjs-graphql`](https://github.com/unlight/prisma-nestjs-graphql): Generates object types, inputs, args, etc. from the Prisma schema for usage with `@nestjs/graphql` module +- [`prisma-nestjs-graphql`](https://github.com/unlight/prisma-nestjs-graphql): Generates object types, inputs, args, etc. from the Prisma Schema for usage with `@nestjs/graphql` module - [`prisma-appsync`](https://github.com/maoosi/prisma-appsync): Generates a full-blown GraphQL API for [AWS AppSync](https://aws.amazon.com/appsync/) - [`prisma-kysely`](https://github.com/valtyr/prisma-kysely): Generates type definitions for Kysely, a TypeScript SQL query builder. This can be useful to perform queries against your database from an edge runtime, or to write more complex SQL queries not possible in Prisma without dropping type safety. - [`prisma-generator-nestjs-dto`](https://github.com/vegardit/prisma-generator-nestjs-dto): Generates DTO and Entity classes with relation `connect` and `create` options for use with [NestJS Resources](https://docs.nestjs.com/recipes/crud-generator) and [@nestjs/swagger](https://www.npmjs.com/package/@nestjs/swagger) diff --git a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx index 0d9e8b85e6..2e5a20b1bc 100644 --- a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx @@ -4,13 +4,13 @@ metaTitle: Prisma Schema Location and Configuration metaDescription: Documentation regarding proper location of Prisma Schema including default naming and multiple files. --- -The default name for the Prisma schema is a single file `schema.prisma` in your `prisma` folder. When your schema is named like this, the Prisma CLI will detect it automatically. +The default name for the Prisma Schema is a single file `schema.prisma` in your `prisma` folder. When your schema is named like this, the Prisma CLI will detect it automatically. > If you are using the [`prismaSchemaFolder` preview feature](#multi-file-prisma-schema) any files in the `prisma/schema` directory are detected automatically. ## Prisma Schema location -The Prisma CLI looks for the Prisma schema in the following locations, in the following order: +The Prisma CLI looks for the Prisma Schema in the following locations, in the following order: 1. The location specified by the [`--schema` flag](/orm/reference/prisma-cli-reference), which is available when you `introspect`, `generate`, `migrate`, and `studio`: @@ -53,7 +53,7 @@ Multi-file Prisma Schema is available via the `prismaSchemaFolder` preview featu ::: -To use multiple Prisma schema files, add a `schema` folder inside of your current `prisma` directory. With the `prismaSchemaFolder` Preview feature enabled, you can add as many files as you want to the `prisma/schema` directory. +To use multiple Prisma Schema files, add a `schema` folder inside of your current `prisma` directory. With the `prismaSchemaFolder` Preview feature enabled, you can add as many files as you want to the `prisma/schema` directory. ``` my-app/ ├─ ... @@ -67,7 +67,7 @@ my-app/ ### How to enable multi-file Prisma schema support -Support for multiple Prisma schema files is currently in preview. To enable the feature, add the `prismaSchemaFolder` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: +Support for multiple Prisma Schema files is currently in preview. To enable the feature, add the `prismaSchemaFolder` feature flag to the `previewFeatures` field of the `generator` block in your Prisma Schema: ```prisma file=schema.prisma showLineNumbers generator client { diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx index 3c8ed75993..970bce8f80 100644 --- a/content/200-orm/100-prisma-schema/10-overview/index.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx @@ -4,7 +4,7 @@ metaTitle: 'Prisma Schema Overview' metaDescription: 'The Prisma schema is the main method of configuration when using Prisma. It is typically called schema.prisma and contains your database connection and data model.' --- -The Prisma schema (or _schema_ for short) is the main method of configuration for your Prisma ORM setup. It consists of the following parts: +The Prisma Schema (or _schema_ for short) is the main method of configuration for your Prisma ORM setup. It consists of the following parts: - [**Data sources**](/orm/prisma-schema/overview/data-sources): Specify the details of the data sources Prisma ORM should connect to (e.g. a PostgreSQL database) - [**Generators**](/orm/prisma-schema/overview/generators): Specifies what clients should be generated based on the data model (e.g. Prisma Client) @@ -14,7 +14,7 @@ It is typically a single file called `schema.prisma` (or multiple files with `.p :::note -Looking to split your schema into multiple files? Multi-file Prisma schema is supported via the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/overview/location#multi-file-prisma-schema) in Prisma ORM 5.15.0 and later. +Looking to split your schema into multiple files? Multi-file Prisma Schema is supported via the [`prismaSchemaFolder` preview feature](/orm/prisma-schema/overview/location#multi-file-prisma-schema) in Prisma ORM 5.15.0 and later. ::: @@ -29,7 +29,7 @@ You can also [use environment variables](#accessing-environment-variables-from-t ## Example -The following is an example of a Prisma schema that specifies: +The following is an example of a Prisma Schema that specifies: - A data source (PostgreSQL or MongoDB) - A generator (Prisma Client) @@ -117,7 +117,7 @@ enum Role { ## Syntax -Prisma schema files are written in Prisma Schema Language (PSL). See the [data sources](/orm/prisma-schema/overview/data-sources), [generators](/orm/prisma-schema/overview/generators), [data model definition**](/orm/prisma-schema/data-model) and of course [Prisma schema API reference](/orm/reference/prisma-schema-reference) pages for details and examples. +Prisma Schema files are written in Prisma Schema Language (PSL). See the [data sources](/orm/prisma-schema/overview/data-sources), [generators](/orm/prisma-schema/overview/generators), [data model definition**](/orm/prisma-schema/data-model) and of course [Prisma Schema API reference](/orm/reference/prisma-schema-reference) pages for details and examples. ### VS Code diff --git a/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx b/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx index f512a7f8ac..c8551900ec 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx +++ b/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx @@ -28,7 +28,7 @@ The `views` preview feature allows you to represent views in your Prisma schema ## Enable the `views` preview feature -Support for views is currently in an early preview. To enable the `views` preview feature, add the `views` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: +Support for views is currently in an early preview. To enable the `views` preview feature, add the `views` feature flag to the `previewFeatures` field of the `generator` block in your Prisma Schema: ```prisma file=schema.prisma highlight=3;add showLineNumbers generator client { diff --git a/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx b/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx index 5585142dfa..af8c523fcc 100644 --- a/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx +++ b/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx @@ -28,7 +28,7 @@ This guide explains how to: ## How to enable the `multiSchema` preview feature -Multi-schema support is currently in preview. To enable the `multiSchema` preview feature, add the `multiSchema` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: +Multi-schema support is currently in preview. To enable the `multiSchema` preview feature, add the `multiSchema` feature flag to the `previewFeatures` field of the `generator` block in your Prisma Schema: ```prisma file=schema.prisma highlight=3;add showLineNumbers generator client { diff --git a/content/200-orm/100-prisma-schema/50-introspection.mdx b/content/200-orm/100-prisma-schema/50-introspection.mdx index b41d630399..0e76630d80 100644 --- a/content/200-orm/100-prisma-schema/50-introspection.mdx +++ b/content/200-orm/100-prisma-schema/50-introspection.mdx @@ -315,7 +315,7 @@ Note that you can rename the [Prisma-ORM level](/orm/prisma-schema/data-model/re ## Introspection with an existing schema -Running `prisma db pull` for relational databases with an existing Prisma schema merges manual changes made to the schema, with changes made in the database. (This functionality has been added for the first time with version 2.6.0.) For MongoDB, Introspection for now is meant to be done only once for the initial data model. Running it repeatedly will lead to loss of custom changes, as the ones listed below. +Running `prisma db pull` for relational databases with an existing Prisma Schema merges manual changes made to the schema, with changes made in the database. (This functionality has been added for the first time with version 2.6.0.) For MongoDB, Introspection for now is meant to be done only once for the initial data model. Running it repeatedly will lead to loss of custom changes, as the ones listed below. Introspection for relational databases maintains the following manual changes: @@ -339,7 +339,7 @@ The following properties of the schema are determined by the database: ### Force overwrite -To overwrite manual changes, and generate a schema based solely on the introspected database and ignore any existing Prisma schema, add the `--force` flag to the `db pull` command: +To overwrite manual changes, and generate a schema based solely on the introspected database and ignore any existing Prisma Schema, add the `--force` flag to the `db pull` command: ```terminal npx prisma db pull --force diff --git a/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx b/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx index 17c169f51f..e16e95a16c 100644 --- a/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx +++ b/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx @@ -34,7 +34,7 @@ Prisma's `postgresqlExtensions` preview feature allows you to represent PostgreS ## How to enable the `postgresqlExtensions` preview feature -Representing PostgreSQL extensions in your Prisma schema is currently a preview feature. To enable the `postgresqlExtensions` preview feature, you will need to add the `postgresqlExtensions` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: +Representing PostgreSQL extensions in your Prisma Schema is currently a preview feature. To enable the `postgresqlExtensions` preview feature, you will need to add the `postgresqlExtensions` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema: ```prisma file=schema.prisma highlight=3;add showLineNumbers generator client { diff --git a/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx b/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx index 05da0817fa..9f6437bee4 100644 --- a/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx +++ b/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx @@ -203,7 +203,7 @@ Your `schema.prisma` and local database now include your team's changes, and the You should commit the following files to source control: - The contents of the `.prisma/migrations` folder, including the `migration_lock.toml` file -- The Prisma schema (`schema.prisma`) +- The Prisma Schema (`schema.prisma`) Source-controlling the `schema.prisma` file is not enough - you must include your migration history. This is because: diff --git a/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx b/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx index a84388c722..f9a6f18728 100644 --- a/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx +++ b/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx @@ -41,7 +41,7 @@ In earlier versions of Prisma ORM, you must instead add a SQL command to your mi ## How to install a PostgreSQL extension as part of a migration -This section describes how to add a SQL command to a migration file to activate a PostgreSQL extension. If you manage PostgreSQL extensions in your Prisma schema with the `postgresqlExtensions` preview feature instead, see [How to migrate PostgreSQL extensions](/orm/prisma-schema/postgresql-extensions#how-to-migrate-postgresql-extensions). +This section describes how to add a SQL command to a migration file to activate a PostgreSQL extension. If you manage PostgreSQL extensions in your Prisma Schema with the `postgresqlExtensions` preview feature instead, see [How to migrate PostgreSQL extensions](/orm/prisma-schema/postgresql-extensions#how-to-migrate-postgresql-extensions). The following example demonstrates how to install the `pgcrypto` extension as part of a migration: diff --git a/content/200-orm/500-reference/200-prisma-cli-reference.mdx b/content/200-orm/500-reference/200-prisma-cli-reference.mdx index a32b58f5f9..dd1a104e42 100644 --- a/content/200-orm/500-reference/200-prisma-cli-reference.mdx +++ b/content/200-orm/500-reference/200-prisma-cli-reference.mdx @@ -320,7 +320,7 @@ The `generate` command is most often used to generate Prisma Client with the `pr 1. Searches the current directory and parent directories to find the applicable `npm` project. It will create a `package.json` file in the current directory if it cannot find one. 2. Installs the `@prisma/client` into the `npm` project if it is not already present. -3. Inspects the current directory to find a Prisma schema to process. It will then generate a customized [Prisma Client](https://github.com/prisma/prisma-client-js) for your project. +3. Inspects the current directory to find a Prisma Schema to process. It will then generate a customized [Prisma Client](https://github.com/prisma/prisma-client-js) for your project. #### Prerequisites diff --git a/content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx b/content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx index 27869d05a4..07b96a63cd 100644 --- a/content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx +++ b/content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx @@ -30,7 +30,7 @@ The following [Preview](/orm/more/releases#preview) feature flags are available | `relationJoins` | [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/22288) | | `nativeDistinct` | [5.7.0](https://github.com/prisma/prisma/releases/tag/5.7.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/22287) | | `omitApi` | [5.13.0](https://github.com/prisma/prisma/releases/tag/5.13.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/23924) | -| `prismaSchemaFolder` | [5.15.0](https://github.com/prisma/prisma/releases/tag/5.15.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/23924) | +| `prismaSchemaFolder` | [5.15.0](https://github.com/prisma/prisma/releases/tag/5.15.0) | [Submit feedback](https://github.com/prisma/prisma/discussions/24413) | To enable a Preview feature, [add the feature flag to the `generator` block](#enabling-a-prisma-client-preview-feature) in your `schema.prisma` file. [Share your feedback on all Preview features on GitHub](https://github.com/prisma/prisma/issues/3108). From e19297dc30143d833cf474952ab39049a4259aaa Mon Sep 17 00:00:00 2001 From: Jan Piotrowski Date: Tue, 4 Jun 2024 15:40:26 +0200 Subject: [PATCH 18/18] Update content/200-orm/100-prisma-schema/10-overview/04-location.mdx --- content/200-orm/100-prisma-schema/10-overview/04-location.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx index 2e5a20b1bc..a2cbdcb400 100644 --- a/content/200-orm/100-prisma-schema/10-overview/04-location.mdx +++ b/content/200-orm/100-prisma-schema/10-overview/04-location.mdx @@ -112,4 +112,4 @@ Our fork of [`dub` by dub.co](https://github.com/prisma/dub) is a great example ### Learn more about the `prismaSchemaFolder` preview feature -To give feedback on the `prismaSchemaFolder` Preview feature, please refer to [our dedicated Github discussion](https://github.com/prisma/prisma/issues/1122). +To give feedback on the `prismaSchemaFolder` Preview feature, please refer to [our dedicated Github discussion](https://github.com/prisma/prisma/discussions/24413).