From f2930e343fe2c0984a383a95690fc220ce723862 Mon Sep 17 00:00:00 2001 From: Nikolas Burk Date: Tue, 30 Sep 2025 11:23:10 +0200 Subject: [PATCH 1/8] move pages in ppg docs --- .../{1100-integrations => 350-integrations}/100-netlify.mdx | 0 .../{1100-integrations => 350-integrations}/200-vercel.mdx | 0 .../{1100-integrations => 350-integrations}/300-idx.mdx | 0 .../{1100-integrations => 350-integrations}/400-mcp-server.mdx | 0 .../700-tooling.mdx => 350-integrations/450-tooling.mdx} | 0 .../{1100-integrations => 350-integrations}/500-vscode.mdx | 0 .../{1100-integrations => 350-integrations}/_category_.json | 0 .../{1100-integrations => 350-integrations}/index.mdx | 0 static/_redirects | 2 ++ 9 files changed, 2 insertions(+) rename content/250-postgres/{1100-integrations => 350-integrations}/100-netlify.mdx (100%) rename content/250-postgres/{1100-integrations => 350-integrations}/200-vercel.mdx (100%) rename content/250-postgres/{1100-integrations => 350-integrations}/300-idx.mdx (100%) rename content/250-postgres/{1100-integrations => 350-integrations}/400-mcp-server.mdx (100%) rename content/250-postgres/{300-database/700-tooling.mdx => 350-integrations/450-tooling.mdx} (100%) rename content/250-postgres/{1100-integrations => 350-integrations}/500-vscode.mdx (100%) rename content/250-postgres/{1100-integrations => 350-integrations}/_category_.json (100%) rename content/250-postgres/{1100-integrations => 350-integrations}/index.mdx (100%) diff --git a/content/250-postgres/1100-integrations/100-netlify.mdx b/content/250-postgres/350-integrations/100-netlify.mdx similarity index 100% rename from content/250-postgres/1100-integrations/100-netlify.mdx rename to content/250-postgres/350-integrations/100-netlify.mdx diff --git a/content/250-postgres/1100-integrations/200-vercel.mdx b/content/250-postgres/350-integrations/200-vercel.mdx similarity index 100% rename from content/250-postgres/1100-integrations/200-vercel.mdx rename to content/250-postgres/350-integrations/200-vercel.mdx diff --git a/content/250-postgres/1100-integrations/300-idx.mdx b/content/250-postgres/350-integrations/300-idx.mdx similarity index 100% rename from content/250-postgres/1100-integrations/300-idx.mdx rename to content/250-postgres/350-integrations/300-idx.mdx diff --git a/content/250-postgres/1100-integrations/400-mcp-server.mdx b/content/250-postgres/350-integrations/400-mcp-server.mdx similarity index 100% rename from content/250-postgres/1100-integrations/400-mcp-server.mdx rename to content/250-postgres/350-integrations/400-mcp-server.mdx diff --git a/content/250-postgres/300-database/700-tooling.mdx b/content/250-postgres/350-integrations/450-tooling.mdx similarity index 100% rename from content/250-postgres/300-database/700-tooling.mdx rename to content/250-postgres/350-integrations/450-tooling.mdx diff --git a/content/250-postgres/1100-integrations/500-vscode.mdx b/content/250-postgres/350-integrations/500-vscode.mdx similarity index 100% rename from content/250-postgres/1100-integrations/500-vscode.mdx rename to content/250-postgres/350-integrations/500-vscode.mdx diff --git a/content/250-postgres/1100-integrations/_category_.json b/content/250-postgres/350-integrations/_category_.json similarity index 100% rename from content/250-postgres/1100-integrations/_category_.json rename to content/250-postgres/350-integrations/_category_.json diff --git a/content/250-postgres/1100-integrations/index.mdx b/content/250-postgres/350-integrations/index.mdx similarity index 100% rename from content/250-postgres/1100-integrations/index.mdx rename to content/250-postgres/350-integrations/index.mdx diff --git a/static/_redirects b/static/_redirects index d6f30752ca..6aba42e553 100644 --- a/static/_redirects +++ b/static/_redirects @@ -633,4 +633,6 @@ /postgres/more/known-limitations /docs/postgres/introduction/overview /postgres/integrations/vscode-extension* /postgres/integrations/vscode:splat +/postgres/database/tooling /postgres/integrations/tooling + ### NO REDIRECTS BELOW THIS LINE. ADD REDIRECTS ABOVE THIS SECTION ### From 7a9d57e68af9b687a7d32c6bc3caaf60db593b21 Mon Sep 17 00:00:00 2001 From: Nikolas Burk Date: Tue, 30 Sep 2025 11:29:58 +0200 Subject: [PATCH 2/8] fix redirect --- static/_redirects | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/static/_redirects b/static/_redirects index 6aba42e553..dafb268bfb 100644 --- a/static/_redirects +++ b/static/_redirects @@ -633,6 +633,8 @@ /postgres/more/known-limitations /docs/postgres/introduction/overview /postgres/integrations/vscode-extension* /postgres/integrations/vscode:splat -/postgres/database/tooling /postgres/integrations/tooling +/postgres/database/tooling /docs/postgres/integrations/tooling + + ### NO REDIRECTS BELOW THIS LINE. ADD REDIRECTS ABOVE THIS SECTION ### From 1e782228e0d977ce1097017e5cb2889c100b55e3 Mon Sep 17 00:00:00 2001 From: Nikolas Burk Date: Tue, 30 Sep 2025 11:43:15 +0200 Subject: [PATCH 3/8] fix internal links --- .../110-import-from-existing-database-postgresql.mdx | 2 +- .../115-import-from-existing-database-mysql.mdx | 2 +- .../250-postgres/300-database/650-direct-connections.mdx | 4 ++-- static/_redirects | 6 +++--- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx b/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx index 14d92e2099..7f32620e37 100644 --- a/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx +++ b/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx @@ -153,7 +153,7 @@ pg_restore \ Once the command completes execution, you will have successfully imported the data from your your existing PostgreSQL database into Prisma Postgres 🎉 -To validate that the import worked, you can use [Prisma Studio](/postgres/database/tooling#viewing-and-editing-data-in-prisma-studio). Either open it in the [Platform Console](https://console.prisma.io) by clicking the **Studio** tab in the left-hand sidenav in your project or run this command to launch Prisma Studio locally: +To validate that the import worked, you can use [Prisma Studio](/postgres/integrations/tooling#viewing-and-editing-data-in-prisma-studio). Either open it in the [Platform Console](https://console.prisma.io) by clicking the **Studio** tab in the left-hand sidenav in your project or run this command to launch Prisma Studio locally: ```terminal npx prisma studio diff --git a/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx b/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx index 52c8461fb9..53e683db6d 100644 --- a/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx +++ b/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx @@ -133,7 +133,7 @@ If you see output like this, it means your data has been successfully exported t :::note -You also can use [Prisma Studio](/postgres/database/tooling#viewing-and-editing-data-in-prisma-studio) and verify whether the migration was successful: +You also can use [Prisma Studio](/postgres/integrations/tooling#viewing-and-editing-data-in-prisma-studio) and verify whether the migration was successful: ```terminal npx prisma studio diff --git a/content/250-postgres/300-database/650-direct-connections.mdx b/content/250-postgres/300-database/650-direct-connections.mdx index 744cbabcfb..5fb2bcccef 100644 --- a/content/250-postgres/300-database/650-direct-connections.mdx +++ b/content/250-postgres/300-database/650-direct-connections.mdx @@ -164,7 +164,7 @@ password: This will start the tunnel on a randomly assigned TCP port. The proxy automatically handles authentication, so any database credentials are accepted. The tunnel also encrypts traffic, meaning clients should be set to not require SSL. -You can now connet to your Prisma Postgres editor using your favorite PostgreSQL client, e.g. `psql` or a GUI like [TablePlus](/postgres/database/tooling#2a-connect-to-prisma-postgres-using-tableplus) or [DataGrip](/postgres/database/tooling#2b-connect-to-prisma-postgres-using-datagrip). To do so, you only need to provide the **`host`** and **`port`** from the output above. The TCP tunnel will handle authentication via the API key in your Prisma Postgres connection URL, so you can omit the values for **`username`** and **`password`**. +You can now connet to your Prisma Postgres editor using your favorite PostgreSQL client, e.g. `psql` or a GUI like [TablePlus](/postgres/integrations/tooling#2a-connect-to-prisma-postgres-using-tableplus) or [DataGrip](/postgres/integrations/tooling#2b-connect-to-prisma-postgres-using-datagrip). To do so, you only need to provide the **`host`** and **`port`** from the output above. The TCP tunnel will handle authentication via the API key in your Prisma Postgres connection URL, so you can omit the values for **`username`** and **`password`**. ### Customizing host and port @@ -176,7 +176,7 @@ npx @prisma/ppg-tunnel --host 127.0.0.1 --port 5432 ### Next steps -The local tunnel enables you to access Prisma Postgres from 3rd party database editors such as Postico, DataGrip, TablePlus and pgAdmin. Learn more in this [section](/postgres/database/tooling). +The local tunnel enables you to access Prisma Postgres from 3rd party database editors such as Postico, DataGrip, TablePlus and pgAdmin. Learn more in this [section](/postgres/integrations/tooling). ### Security considerations diff --git a/static/_redirects b/static/_redirects index dafb268bfb..46aa29fc88 100644 --- a/static/_redirects +++ b/static/_redirects @@ -542,7 +542,7 @@ /postgres/connection-pooling /docs/postgres/database/connection-pooling /postgres/backups /docs/postgres/database/backups /postgres/tcp-tunnel /docs/postgres/database/tcp-tunnel -/postgres/tooling /docs/postgres/database/tooling +/postgres/tooling /docs/postgres/integrations/tooling /postgres/caching /docs/postgres/database/caching /optimize/recommendations/excessive-number-of-rows-returned /docs/postgres/query-optimization/recommendations/excessive-number-of-rows-returned @@ -619,7 +619,7 @@ /postgres/connection-pooling* /docs/postgres/database/connection-pooling /postgres/backups* /docs/postgres/database/backups /postgres/tcp-tunnel* /docs/postgres/database/tcp-tunnel -/postgres/tooling* /docs/postgres/database/tooling +/postgres/tooling* /docs/postgres/integrations/tooling /postgres/api-reference* /docs/postgres/database/api-reference /optimize/recommendations/* /docs/postgres/query-optimization/recommendations @@ -633,7 +633,7 @@ /postgres/more/known-limitations /docs/postgres/introduction/overview /postgres/integrations/vscode-extension* /postgres/integrations/vscode:splat -/postgres/database/tooling /docs/postgres/integrations/tooling +/postgres/integrations/tooling /docs/postgres/integrations/tooling From 02ade476ce46be480cea49bf864b20ffef2af174 Mon Sep 17 00:00:00 2001 From: Nikolas Date: Tue, 30 Sep 2025 11:51:28 +0200 Subject: [PATCH 4/8] Update content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- .../110-import-from-existing-database-postgresql.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx b/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx index 7f32620e37..757409a306 100644 --- a/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx +++ b/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx @@ -151,7 +151,7 @@ pg_restore \ && echo "-complete-" ``` -Once the command completes execution, you will have successfully imported the data from your your existing PostgreSQL database into Prisma Postgres 🎉 +Once the command completes execution, you will have successfully imported the data from your existing PostgreSQL database into Prisma Postgres 🎉 To validate that the import worked, you can use [Prisma Studio](/postgres/integrations/tooling#viewing-and-editing-data-in-prisma-studio). Either open it in the [Platform Console](https://console.prisma.io) by clicking the **Studio** tab in the left-hand sidenav in your project or run this command to launch Prisma Studio locally: From 0a04da0bf81723fd6d56c90eba5b0e71b68454dc Mon Sep 17 00:00:00 2001 From: Nikolas Burk Date: Tue, 30 Sep 2025 12:58:21 +0200 Subject: [PATCH 5/8] update tooling page title --- .../{450-tooling.mdx => 450-viewing-data.mdx} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename content/250-postgres/350-integrations/{450-tooling.mdx => 450-viewing-data.mdx} (97%) diff --git a/content/250-postgres/350-integrations/450-tooling.mdx b/content/250-postgres/350-integrations/450-viewing-data.mdx similarity index 97% rename from content/250-postgres/350-integrations/450-tooling.mdx rename to content/250-postgres/350-integrations/450-viewing-data.mdx index 6f231f9c2c..5fb61aaa8e 100644 --- a/content/250-postgres/350-integrations/450-tooling.mdx +++ b/content/250-postgres/350-integrations/450-viewing-data.mdx @@ -1,7 +1,7 @@ --- -title: 'Tooling' -metaTitle: 'Tooling' -metaDescription: 'Learn about connecting directly to your database via TCP tunnel' +title: 'Viewing data' +metaTitle: 'Viewing data' +metaDescription: 'Viewing and editing data in Prisma Postrgres via Prisma Studio or other database GUIs.' tocDepth: 3 toc: true --- From 64143d9f860770ea8612d4fab9899d617afd8464 Mon Sep 17 00:00:00 2001 From: Nikolas Burk Date: Tue, 30 Sep 2025 13:07:19 +0200 Subject: [PATCH 6/8] update links --- .../110-import-from-existing-database-postgresql.mdx | 2 +- .../115-import-from-existing-database-mysql.mdx | 2 +- content/250-postgres/300-database/650-direct-connections.mdx | 4 ++-- static/_redirects | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx b/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx index 757409a306..310401625f 100644 --- a/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx +++ b/content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx @@ -153,7 +153,7 @@ pg_restore \ Once the command completes execution, you will have successfully imported the data from your existing PostgreSQL database into Prisma Postgres 🎉 -To validate that the import worked, you can use [Prisma Studio](/postgres/integrations/tooling#viewing-and-editing-data-in-prisma-studio). Either open it in the [Platform Console](https://console.prisma.io) by clicking the **Studio** tab in the left-hand sidenav in your project or run this command to launch Prisma Studio locally: +To validate that the import worked, you can use [Prisma Studio](/postgres/integrations/viewing-data#viewing-and-editing-data-in-prisma-studio). Either open it in the [Platform Console](https://console.prisma.io) by clicking the **Studio** tab in the left-hand sidenav in your project or run this command to launch Prisma Studio locally: ```terminal npx prisma studio diff --git a/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx b/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx index 53e683db6d..795c4c8634 100644 --- a/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx +++ b/content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx @@ -133,7 +133,7 @@ If you see output like this, it means your data has been successfully exported t :::note -You also can use [Prisma Studio](/postgres/integrations/tooling#viewing-and-editing-data-in-prisma-studio) and verify whether the migration was successful: +You also can use [Prisma Studio](/postgres/integrations/viewing-data#viewing-and-editing-data-in-prisma-studio) and verify whether the migration was successful: ```terminal npx prisma studio diff --git a/content/250-postgres/300-database/650-direct-connections.mdx b/content/250-postgres/300-database/650-direct-connections.mdx index 5fb2bcccef..23455a470f 100644 --- a/content/250-postgres/300-database/650-direct-connections.mdx +++ b/content/250-postgres/300-database/650-direct-connections.mdx @@ -164,7 +164,7 @@ password: This will start the tunnel on a randomly assigned TCP port. The proxy automatically handles authentication, so any database credentials are accepted. The tunnel also encrypts traffic, meaning clients should be set to not require SSL. -You can now connet to your Prisma Postgres editor using your favorite PostgreSQL client, e.g. `psql` or a GUI like [TablePlus](/postgres/integrations/tooling#2a-connect-to-prisma-postgres-using-tableplus) or [DataGrip](/postgres/integrations/tooling#2b-connect-to-prisma-postgres-using-datagrip). To do so, you only need to provide the **`host`** and **`port`** from the output above. The TCP tunnel will handle authentication via the API key in your Prisma Postgres connection URL, so you can omit the values for **`username`** and **`password`**. +You can now connet to your Prisma Postgres editor using your favorite PostgreSQL client, e.g. `psql` or a GUI like [TablePlus](/postgres/integrations/viewing-data#2a-connect-to-prisma-postgres-using-tableplus) or [DataGrip](/postgres/integrations/viewing-data#2b-connect-to-prisma-postgres-using-datagrip). To do so, you only need to provide the **`host`** and **`port`** from the output above. The TCP tunnel will handle authentication via the API key in your Prisma Postgres connection URL, so you can omit the values for **`username`** and **`password`**. ### Customizing host and port @@ -176,7 +176,7 @@ npx @prisma/ppg-tunnel --host 127.0.0.1 --port 5432 ### Next steps -The local tunnel enables you to access Prisma Postgres from 3rd party database editors such as Postico, DataGrip, TablePlus and pgAdmin. Learn more in this [section](/postgres/integrations/tooling). +The local tunnel enables you to access Prisma Postgres from 3rd party database editors such as Postico, DataGrip, TablePlus and pgAdmin. Learn more in this [section](/postgres/integrations/viewing-data). ### Security considerations diff --git a/static/_redirects b/static/_redirects index 46aa29fc88..e2c2eb925f 100644 --- a/static/_redirects +++ b/static/_redirects @@ -633,8 +633,8 @@ /postgres/more/known-limitations /docs/postgres/introduction/overview /postgres/integrations/vscode-extension* /postgres/integrations/vscode:splat -/postgres/integrations/tooling /docs/postgres/integrations/tooling - +/postgres/database/tooling /docs/postgres/integrations/viewing-data +/postgres/integrations/tooling /docs/postgres/integrations/viewing-data ### NO REDIRECTS BELOW THIS LINE. ADD REDIRECTS ABOVE THIS SECTION ### From df135cc1ba9c93cd7c3079a476bcb1e4c26a349f Mon Sep 17 00:00:00 2001 From: Nikolas Date: Tue, 30 Sep 2025 13:20:57 +0200 Subject: [PATCH 7/8] Update content/250-postgres/300-database/650-direct-connections.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- content/250-postgres/300-database/650-direct-connections.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/250-postgres/300-database/650-direct-connections.mdx b/content/250-postgres/300-database/650-direct-connections.mdx index 23455a470f..c74f0e37aa 100644 --- a/content/250-postgres/300-database/650-direct-connections.mdx +++ b/content/250-postgres/300-database/650-direct-connections.mdx @@ -164,7 +164,7 @@ password: This will start the tunnel on a randomly assigned TCP port. The proxy automatically handles authentication, so any database credentials are accepted. The tunnel also encrypts traffic, meaning clients should be set to not require SSL. -You can now connet to your Prisma Postgres editor using your favorite PostgreSQL client, e.g. `psql` or a GUI like [TablePlus](/postgres/integrations/viewing-data#2a-connect-to-prisma-postgres-using-tableplus) or [DataGrip](/postgres/integrations/viewing-data#2b-connect-to-prisma-postgres-using-datagrip). To do so, you only need to provide the **`host`** and **`port`** from the output above. The TCP tunnel will handle authentication via the API key in your Prisma Postgres connection URL, so you can omit the values for **`username`** and **`password`**. +You can now connect to your Prisma Postgres editor using your favorite PostgreSQL client, e.g. `psql` or a GUI like [TablePlus](/postgres/integrations/viewing-data#2a-connect-to-prisma-postgres-using-tableplus) or [DataGrip](/postgres/integrations/viewing-data#2b-connect-to-prisma-postgres-using-datagrip). To do so, you only need to provide the **`host`** and **`port`** from the output above. The TCP tunnel will handle authentication via the API key in your Prisma Postgres connection URL, so you can omit the values for **`username`** and **`password`.** ### Customizing host and port From 0d3b5da2c42a53f5cf418965b203d17cd1b6ce4c Mon Sep 17 00:00:00 2001 From: Nikolas Date: Tue, 30 Sep 2025 13:41:36 +0200 Subject: [PATCH 8/8] Update content/250-postgres/350-integrations/450-viewing-data.mdx --- content/250-postgres/350-integrations/450-viewing-data.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/250-postgres/350-integrations/450-viewing-data.mdx b/content/250-postgres/350-integrations/450-viewing-data.mdx index 5fb61aaa8e..5e490ad917 100644 --- a/content/250-postgres/350-integrations/450-viewing-data.mdx +++ b/content/250-postgres/350-integrations/450-viewing-data.mdx @@ -1,7 +1,7 @@ --- title: 'Viewing data' metaTitle: 'Viewing data' -metaDescription: 'Viewing and editing data in Prisma Postrgres via Prisma Studio or other database GUIs.' +metaDescription: 'Viewing and editing data in Prisma Postgres via Prisma Studio or other database GUIs.' tocDepth: 3 toc: true ---