Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restructuring the documentation #5508

Merged
merged 110 commits into from
Dec 7, 2023
Merged
Changes from 1 commit
Commits
Show all changes
110 commits
Select commit Hold shift + click to select a range
312fb38
update: hidden prop on nav item
nilubava Nov 22, 2023
0487ec3
Update config.ts
nikolasburk Nov 24, 2023
9ae6b9e
arranged the ORM -> OVERVIEW section
nikolasburk Nov 24, 2023
1240e60
arranged the ORM -> PRISMA CLIENT section
nikolasburk Nov 24, 2023
11b5578
arranged the ORM -> PRISMA MIGRATE section
nikolasburk Nov 24, 2023
7917f09
arranged the ORM -> PRISMA SCHEMA section
nikolasburk Nov 24, 2023
d339459
arranged the ORM -> TOOLS and REFERENCE sections; MORE still needs so…
nikolasburk Nov 24, 2023
6d7dd65
finalized structure but with bug
nikolasburk Nov 27, 2023
32aa217
cleaned up About section
nikolasburk Nov 27, 2023
c75c784
fix build error
nikolasburk Nov 27, 2023
5163e9d
Merge branch 'main' into docs-restructure
nikolasburk Nov 27, 2023
46aaf4c
reorder top-level nav
nikolasburk Nov 27, 2023
84419bc
fix typo
nikolasburk Nov 27, 2023
fdfffed
removed <span> elements for concepts, guides and api reference
nikolasburk Nov 27, 2023
701465d
Merge branch 'main' into docs-restructure-links-check
nikolasburk Nov 28, 2023
93eff14
add redirects (still has 40 TODOs)
nikolasburk Nov 28, 2023
76eb239
fix json
nikolasburk Nov 28, 2023
2957e0a
add redirects for all TODOs
nikolasburk Nov 28, 2023
5655626
move folder with db connectors one level up
nikolasburk Nov 28, 2023
0850e44
fix remaining redirect issues
nikolasburk Nov 29, 2023
5ad651f
fix absolute links
nikolasburk Nov 29, 2023
8a69e49
hack to be able to test redirects (#5512)
janpio Nov 30, 2023
7e4dea9
add missing redirects
nikolasburk Nov 30, 2023
fdf93c3
resolve merge conflict
nikolasburk Nov 30, 2023
00979bb
undo hack for redirects
janpio Nov 30, 2023
8f0f0b3
Restructuring the documentation (2) (#5501)
nikolasburk Nov 30, 2023
cc5d708
fix link
janpio Nov 30, 2023
1cda985
Merge branch 'main' into docs-restructure-links-check
nikolasburk Dec 1, 2023
3e80013
fix links on landing page
nikolasburk Dec 1, 2023
e74384f
fix connect-sql-server.png
nikolasburk Dec 1, 2023
bbd7271
fix prisma-db-pull-generate-schema.png
nikolasburk Dec 1, 2023
bffd1da
fix migrate-mapping.png
nikolasburk Dec 1, 2023
f776ef6
fix data-platform/accelerate links
nikolasburk Dec 1, 2023
c9f46a5
fix data-platform/pulse links
nikolasburk Dec 1, 2023
bccc7b1
fix data-platform/classic-projects links
nikolasburk Dec 1, 2023
a0721dc
fix data-platform/data-proxy links
nikolasburk Dec 1, 2023
a254682
fix data-platform/cloud-projects links
nikolasburk Dec 1, 2023
135161c
fix /docs/orm/overview/introduction/databases links
nikolasburk Dec 1, 2023
d77b126
fix broken links on landing page
nikolasburk Dec 1, 2023
c415dbd
fix broken database links on landing page
nikolasburk Dec 1, 2023
22f7193
fix broken orm/prisma-client/deploymen links
nikolasburk Dec 1, 2023
6ca8e3e
fix broken /orm/prisma-client/deployment/serverles/ links
nikolasburk Dec 1, 2023
4ce1cb0
fix broken orm/prisma-schema/features-without-psl-equivalent links
nikolasburk Dec 1, 2023
bce62ea
fix broken orm/prisma-schema/names-in-underlying-database links
nikolasburk Dec 1, 2023
a1ac55e
fix broken orm/prisma-schema/relations links
nikolasburk Dec 1, 2023
19bb6bb
fix broken /orm/reference/supported-databases links
nikolasburk Dec 1, 2023
286018f
fix broken /platform/classic-projects/platform/billing/plans-and-quot…
nikolasburk Dec 1, 2023
d79edba
fix broken /platform/classic-projects/contact-support links
nikolasburk Dec 1, 2023
49c0643
fix broken /platform/classic-projects/about/releases links
nikolasburk Dec 1, 2023
7a24ab5
fix broken platform/classic-projects/about/limits-and-status links
nikolasburk Dec 1, 2023
1c16b17
fix broken /platform/classic-projects/about links
nikolasburk Dec 1, 2023
aee3f78
fix broken /orm/reference/database-reference/supported-databases links
nikolasburk Dec 1, 2023
6e83591
fixed all links on introspection page
nikolasburk Dec 1, 2023
a638174
fix broken /orm/prisma-schema/indexes links
nikolasburk Dec 1, 2023
75d2c6a
fix broken /orm/prisma-schema/generators links
nikolasburk Dec 1, 2023
8b66b5b
fix broken orm/prisma-schema/data-sources links
nikolasburk Dec 1, 2023
68bf831
fix broken /orm/prisma-schema/data-model/orm/reference/database-featu…
nikolasburk Dec 1, 2023
0e34fab
fix broken /orm/prisma-schema/data-model/data-model links
nikolasburk Dec 1, 2023
20f3dc9
fix broken /orm/prisma-migrate/workflows/shadow-database links
nikolasburk Dec 1, 2023
b3eecb6
fix broken prisma migrate links
nikolasburk Dec 1, 2023
647b212
fix broken /orm/prisma-migrate/workflows/deploy-db.png links
nikolasburk Dec 1, 2023
0201b7a
fix broken /orm/prisma-migrate/understanding-prisma-migrate/prisma-mi…
nikolasburk Dec 1, 2023
bcaf856
fix broken /orm/prisma-migrate/supported-types-and-db-features links
nikolasburk Dec 1, 2023
2d38073
fix broken prisma migrate links
nikolasburk Dec 1, 2023
49c8424
fix broken prisma migrate links
nikolasburk Dec 1, 2023
83a639f
fix a bunch of broken prisma client links
nikolasburk Dec 1, 2023
99ed654
fix a bunch of broken prisma client links
nikolasburk Dec 1, 2023
b5e4d26
resolve merge conflict
nikolasburk Dec 1, 2023
bce5b16
fix remaining links
nikolasburk Dec 1, 2023
9d953fd
Merge branch 'update/hide-nav-item' into docs-restructure-links-check
nikolasburk Dec 4, 2023
cdfa05a
hide Platform and About tabs
nikolasburk Dec 4, 2023
d07d0a7
start fixing index pages and polishing
nikolasburk Dec 4, 2023
d6616f0
polished orm/overview
nikolasburk Dec 4, 2023
1f7c07e
polished orm/prisma-client
nikolasburk Dec 4, 2023
e2b7a42
polished orm/prisma-migrate
nikolasburk Dec 4, 2023
d456ffe
polished orm/prisma-migrate
nikolasburk Dec 4, 2023
f34375d
polished orm/prisma-schema
nikolasburk Dec 4, 2023
2d1a17a
polished orm/tools
nikolasburk Dec 4, 2023
5aafb85
polished orm/reference
nikolasburk Dec 4, 2023
3af8653
polished orm
nikolasburk Dec 4, 2023
fa2c41b
polished orm
nikolasburk Dec 4, 2023
0974e57
polished orm
nikolasburk Dec 4, 2023
08fa924
polished accelerate and pulse
nikolasburk Dec 4, 2023
8c5c1e4
polished accelerate and pulse
nikolasburk Dec 4, 2023
281b765
Merge branch 'main' into docs-restructure-links-check
nikolasburk Dec 4, 2023
3a87c54
polished accelerate and pulse
nikolasburk Dec 4, 2023
e786109
resolve merge conflict
nikolasburk Dec 5, 2023
bff8824
Update content/100-getting-started/02-setup-prisma/200-add-to-existin…
nikolasburk Dec 5, 2023
23030fc
reorder in sidenav: schema -> client -> migrate
nikolasburk Dec 5, 2023
dceeeb8
Merge branch 'docs-restructure-links-check' of github.com:prisma/docs…
nikolasburk Dec 5, 2023
80f7d70
fix index pages for client and migrate
nikolasburk Dec 5, 2023
0238a0c
Add subsections list to all index pages (#5520)
janpio Dec 5, 2023
63ea2ae
unhide platform tab
nikolasburk Dec 5, 2023
c859dbf
more polishing
nikolasburk Dec 5, 2023
7117969
landing page for Platform tab
nikolasburk Dec 6, 2023
85ca890
remove earlyaccess prop from frontmatter (and query because the app d…
nikolasburk Dec 6, 2023
831852c
Update bucketName for platform
carlagn Dec 6, 2023
83398fa
resolve merge conflict
nikolasburk Dec 7, 2023
ffbd7de
fix broken links from link checker
nikolasburk Dec 7, 2023
c2e7404
fix broken links from link checker
nikolasburk Dec 7, 2023
eb69744
fix broken links from link checker
nikolasburk Dec 7, 2023
1587108
fix broken links from link checker
nikolasburk Dec 7, 2023
dfc8f88
fix broken links from link checker
nikolasburk Dec 7, 2023
a623f83
fix broken links from link checker
nikolasburk Dec 7, 2023
0d2c8e1
fix broken links from link checker
nikolasburk Dec 7, 2023
4b98a2c
fix broken links from link checker
nikolasburk Dec 7, 2023
ee9f6bc
fix broken links from link checker
nikolasburk Dec 7, 2023
ecdaa58
fix styling issue in top block on type safety index page
nikolasburk Dec 7, 2023
fd0c51a
add subsections to index pages
nikolasburk Dec 7, 2023
3083c89
add fastify for spellcheck
nikolasburk Dec 7, 2023
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
removed <span> elements for concepts, guides and api reference
nikolasburk committed Nov 27, 2023
commit fdfffed15f4b2532af075a38bd31c2484f431289
Original file line number Diff line number Diff line change
@@ -388,8 +388,8 @@ Prisma's data model is a declarative representation of your database schema and

Right now, there's a few minor "issues" with the data model:

- The `User` relation field is uppercased and therefore doesn't adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) <span class="api"></span>. To express more "semantics", it would also be nice if this field was called `author` to _describe_ the relationship between `User` and `Post` better.
- The `Post` and `Profile` relation fields on `User` as well as the `User` relation field on `Profile` are all uppercased. To adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) <span class="api"></span>, both fields should be lowercased to `post`, `profile` and `user`.
- The `User` relation field is uppercased and therefore doesn't adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) . To express more "semantics", it would also be nice if this field was called `author` to _describe_ the relationship between `User` and `Post` better.
- The `Post` and `Profile` relation fields on `User` as well as the `User` relation field on `Profile` are all uppercased. To adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) , both fields should be lowercased to `post`, `profile` and `user`.
- Even after lowercasing, the `post` field on `User` is still slightly misnamed. That's because it actually refers to a [list](/concepts/components/prisma-schema/data-model#type-modifiers) of posts – a better name therefore would be the plural form: `posts`.

These changes are relevant for the generated Prisma Client API where using lowercased relation fields `author`, `posts`, `profile` and `user` will feel more natural and idiomatic to JavaScript/TypeScript developers. You can therefore [configure your Prisma Client API](/concepts/components/prisma-client/working-with-prismaclient/use-custom-model-and-field-names).
@@ -423,7 +423,7 @@ model User {
}
```

In this example, the database schema did follow the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) <span class="api"></span> for Prisma models (only the virtual relation fields that were generated from introspection did not adhere to them and needed adjustment). This optimizes the ergonomics of the generated Prisma Client API.
In this example, the database schema did follow the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) for Prisma models (only the virtual relation fields that were generated from introspection did not adhere to them and needed adjustment). This optimizes the ergonomics of the generated Prisma Client API.

<details>
<summary> Using custom model and field names </summary>
@@ -529,16 +529,16 @@ model User {

<Admonition>

Refer to the [Prisma schema reference](/reference/api-reference/prisma-schema-reference) <span class="api"></span> for detailed information about the schema definition.
Refer to the [Prisma schema reference](/reference/api-reference/prisma-schema-reference) for detailed information about the schema definition.

</Admonition>

Prisma's data model is a declarative representation of your database schema and serves as the foundation for the generated Prisma Client library. Your Prisma Client instance will expose queries that are _tailored_ to these models.

Right now, there's a few minor "issues" with the data model:

- The `User` relation field is uppercased and therefore doesn't adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) <span class="api"></span>. To express more "semantics", it would also be nice if this field was called `author` to _describe_ the relationship between `User` and `Post` better.
- The `Post` and `Profile` relation fields on `User` as well as the `User` relation field on `Profile` are all uppercased. To adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) <span class="api"></span>, both fields should be lowercased to `post`, `profile` and `user`.
- The `User` relation field is uppercased and therefore doesn't adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) . To express more "semantics", it would also be nice if this field was called `author` to _describe_ the relationship between `User` and `Post` better.
- The `Post` and `Profile` relation fields on `User` as well as the `User` relation field on `Profile` are all uppercased. To adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) , both fields should be lowercased to `post`, `profile` and `user`.
- Even after lowercasing, the `post` field on `User` is still slightly misnamed. That's because it actually refers to a [list](/concepts/components/prisma-schema/data-model#type-modifiers) of posts – a better name therefore would be the plural form: `posts`.

These changes are relevant for the generated Prisma Client API where using lowercased relation fields `author`, `posts`, `profile` and `user` will feel more natural and idiomatic to JavaScript/TypeScript developers. You can therefore [configure your Prisma Client API](/concepts/components/prisma-client/working-with-prismaclient/use-custom-model-and-field-names).
@@ -574,7 +574,7 @@ model User {
}
```

In this example, the database schema did follow the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) <span class="api"></span> for Prisma models (only the virtual relation fields that were generated from introspection did not adhere to them and needed adjustment). This optimizes the ergonomics of the generated Prisma Client API.
In this example, the database schema did follow the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) for Prisma models (only the virtual relation fields that were generated from introspection did not adhere to them and needed adjustment). This optimizes the ergonomics of the generated Prisma Client API.

Sometimes though, you may want to make additional changes to the names of the columns and tables that are exposed in the Prisma Client API. A common example is to translate _snake_case_ notation which is often used in database schemas into _PascalCase_ and _camelCase_ notations which feel more natural for JavaScript/TypeScript developers.

@@ -675,8 +675,8 @@ Prisma's data model is a declarative representation of your database schema and

Right now, there's a few minor "issues" with the data model:

- The `User` relation field is uppercased and therefore doesn't adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) <span class="api"></span>. To express more "semantics", it would also be nice if this field was called `author` to _describe_ the relationship between `User` and `Post` better.
- The `Post` and `Profile` relation fields on `User` as well as the `User` relation field on `Profile` are all uppercased. To adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) <span class="api"></span>, both fields should be lowercased to `post`, `profile` and `user`.
- The `User` relation field is uppercased and therefore doesn't adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) . To express more "semantics", it would also be nice if this field was called `author` to _describe_ the relationship between `User` and `Post` better.
- The `Post` and `Profile` relation fields on `User` as well as the `User` relation field on `Profile` are all uppercased. To adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) , both fields should be lowercased to `post`, `profile` and `user`.
- Even after lowercasing, the `post` field on `User` is still slightly misnamed. That's because it actually refers to a [list](/concepts/components/prisma-schema/data-model#type-modifiers) of posts – a better name therefore would be the plural form: `posts`.

These changes are relevant for the generated Prisma Client API where using lowercased relation fields `author`, `posts`, `profile` and `user` will feel more natural and idiomatic to JavaScript/TypeScript developers. You can therefore [configure your Prisma Client API](/concepts/components/prisma-client/working-with-prismaclient/use-custom-model-and-field-names).
@@ -710,7 +710,7 @@ model User {
}
```

In this example, the database schema did follow the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) <span class="api"></span> for Prisma models (only the virtual relation fields that were generated from introspection did not adhere to them and needed adjustment). This optimizes the ergonomics of the generated Prisma Client API.
In this example, the database schema did follow the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) for Prisma models (only the virtual relation fields that were generated from introspection did not adhere to them and needed adjustment). This optimizes the ergonomics of the generated Prisma Client API.

<details>
<summary> Using custom model and field names </summary>
@@ -815,7 +815,7 @@ model User {

<Admonition>

Refer to the [Prisma schema reference](/reference/api-reference/prisma-schema-reference) <span class="api"></span> for detailed information about the schema definition.
Refer to the [Prisma schema reference](/reference/api-reference/prisma-schema-reference) for detailed information about the schema definition.

</Admonition>

@@ -865,7 +865,7 @@ Prisma Migrate will now keep the manually added relation fields.

Because relation fields are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database.

In this example, the database schema follows the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) <span class="api"></span> for Prisma models. This optimizes the ergonomics of the generated Prisma Client API.
In this example, the database schema follows the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) for Prisma models. This optimizes the ergonomics of the generated Prisma Client API.

<details>
<summary> Using custom model and field names </summary>
@@ -971,8 +971,8 @@ Prisma's data model is a declarative representation of your database schema and

Right now, there's a few minor "issues" with the data model:

- The `User` relation field is uppercased and therefore doesn't adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) <span class="api"></span>. To express more "semantics", it would also be nice if this field was called `author` to _describe_ the relationship between `User` and `Post` better.
- The `Post` and `Profile` relation fields on `User` as well as the `User` relation field on `Profile` are all uppercased. To adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) <span class="api"></span>, both fields should be lowercased to `post`, `profile` and `user`.
- The `User` relation field is uppercased and therefore doesn't adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) . To express more "semantics", it would also be nice if this field was called `author` to _describe_ the relationship between `User` and `Post` better.
- The `Post` and `Profile` relation fields on `User` as well as the `User` relation field on `Profile` are all uppercased. To adhere to Prisma's [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions-1) , both fields should be lowercased to `post`, `profile` and `user`.
- Even after lowercasing, the `post` field on `User` is still slightly misnamed. That's because it actually refers to a [list](/concepts/components/prisma-schema/data-model#type-modifiers) of posts – a better name therefore would be the plural form: `posts`.

These changes are relevant for the generated Prisma Client API where using lowercased relation fields `author`, `posts`, `profile` and `user` will feel more natural and idiomatic to JavaScript/TypeScript developers. You can therefore [configure your Prisma Client API](/concepts/components/prisma-client/working-with-prismaclient/use-custom-model-and-field-names).
@@ -1006,7 +1006,7 @@ model User {
}
```

In this example, the database schema did follow the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) <span class="api"></span> for Prisma models (only the virtual relation fields that were generated from introspection did not adhere to them and needed adjustment). This optimizes the ergonomics of the generated Prisma Client API.
In this example, the database schema did follow the [naming conventions](/reference/api-reference/prisma-schema-reference#naming-conventions) for Prisma models (only the virtual relation fields that were generated from introspection did not adhere to them and needed adjustment). This optimizes the ergonomics of the generated Prisma Client API.

<details>
<summary> Using custom model and field names </summary>
Original file line number Diff line number Diff line change
@@ -7,7 +7,7 @@ tocDepth: 4

## Default built-in drivers

One of Prisma Client's components is the [Query Engine](./prisma-engines/query-engine) <span class="concept"></span>. The Query Engine is responsible for transforming Prisma Client queries to SQL statements. The Query Engine connects to your database using the included drivers that don't require additional setup. The built-in drivers use TCP connections to connect to the database.
One of Prisma Client's components is the [Query Engine](./prisma-engines/query-engine) . The Query Engine is responsible for transforming Prisma Client queries to SQL statements. The Query Engine connects to your database using the included drivers that don't require additional setup. The built-in drivers use TCP connections to connect to the database.

![Query flow from the user application to the database with Prisma Client](./images/drivers/qe-query-execution-flow.png)

Original file line number Diff line number Diff line change
@@ -9,7 +9,7 @@ tocDepth: 3

The PostgreSQL data source connector connects Prisma to a [PostgreSQL](https://www.postgresql.org/) database server.

By default, the PostgreSQL connector contains a database driver responsible for connecting to your database. You can use a [driver adapter](/concepts/components/database-drivers#driver-adapters) <span class="concept"></span> (Preview) to connect to your database using a JavaScript database driver from Prisma Client.
By default, the PostgreSQL connector contains a database driver responsible for connecting to your database. You can use a [driver adapter](/concepts/components/database-drivers#driver-adapters) (Preview) to connect to your database using a JavaScript database driver from Prisma Client.

</TopBlock>

@@ -210,7 +210,7 @@ The PostgreSQL connector maps the [scalar types](/concepts/components/prisma-sch
| Composite types | Not yet | n/a | | |
| Domain types | Not yet | n/a | | |

[Introspection](/concepts/components/introspection) adds native database types that are **not yet supported** as [`Unsupported`](/reference/api-reference/prisma-schema-reference#unsupported) <span class="api"></span> fields:
[Introspection](/concepts/components/introspection) adds native database types that are **not yet supported** as [`Unsupported`](/reference/api-reference/prisma-schema-reference#unsupported) fields:

```prisma file=schema.prisma
model Device {
Original file line number Diff line number Diff line change
@@ -9,7 +9,7 @@ tocDepth: 3

The MySQL data source connector connects Prisma to a [MySQL](https://www.mysql.com/) database server.

By default, the MySQL connector contains a database driver responsible for connecting to your database. You can use a [driver adapter](/concepts/components/database-drivers#driver-adapters) <span class="concept"></span> (Preview) to connect to your database using a JavaScript database driver from Prisma Client.
By default, the MySQL connector contains a database driver responsible for connecting to your database. You can use a [driver adapter](/concepts/components/database-drivers#driver-adapters) (Preview) to connect to your database using a JavaScript database driver from Prisma Client.

</TopBlock>

@@ -191,7 +191,7 @@ When introspecting a MySQL database, the database types are mapped to Prisma acc
| `multipolygon` | `Unsupported` | Not yet | |
| `geometrycollection` | `Unsupported` | Not yet | |

[Introspection](/concepts/components/introspection) adds native database types that are **not yet supported** as [`Unsupported`](/reference/api-reference/prisma-schema-reference#unsupported) <span class="api"></span> fields:
[Introspection](/concepts/components/introspection) adds native database types that are **not yet supported** as [`Unsupported`](/reference/api-reference/prisma-schema-reference#unsupported) fields:

```prisma file=schema.prisma
model Device {
Original file line number Diff line number Diff line change
@@ -9,7 +9,7 @@ tocDepth: 3

The SQLite data source connector connects Prisma to a [SQLite](https://www.sqlite.org/) database file. These files always have the file ending `.db` (e.g.: `dev.db`).

By default, the SQLite connector contains a database driver responsible for connecting to your database. You can use a [driver adapter](/concepts/components/database-drivers#driver-adapters) <span class="concept"></span> (Preview) to connect to your database using a JavaScript database driver from Prisma Client.
By default, the SQLite connector contains a database driver responsible for connecting to your database. You can use a [driver adapter](/concepts/components/database-drivers#driver-adapters) (Preview) to connect to your database using a JavaScript database driver from Prisma Client.

</TopBlock>

Original file line number Diff line number Diff line change
@@ -564,7 +564,7 @@ When introspecting a MongoDB database, Prisma uses the relevant [scalar types](/
| ------------------------- | -------- | :-------: | :----------------------------- | :---- |
| `objectId` | `String` | ✔️ | `@db.ObjectId` | |

[Introspection](/concepts/components/introspection) adds native database types that are **not yet supported** as [`Unsupported`](/reference/api-reference/prisma-schema-reference#unsupported) <span class="api"></span> fields:
[Introspection](/concepts/components/introspection) adds native database types that are **not yet supported** as [`Unsupported`](/reference/api-reference/prisma-schema-reference#unsupported) fields:

```prisma file=schema.prisma
model Example {
Loading