Skip to content

Commit 4d4e3e6

Browse files
authored
Merge branch 'main' into feat/DC-5512-new-navbar
2 parents 940b43b + 9f6d249 commit 4d4e3e6

File tree

12 files changed

+14
-10
lines changed

12 files changed

+14
-10
lines changed

content/100-getting-started/03-prisma-postgres/110-import-from-existing-database-postgresql.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -151,9 +151,9 @@ pg_restore \
151151
&& echo "-complete-"
152152
```
153153

154-
Once the command completes execution, you will have successfully imported the data from your your existing PostgreSQL database into Prisma Postgres 🎉
154+
Once the command completes execution, you will have successfully imported the data from your existing PostgreSQL database into Prisma Postgres 🎉
155155

156-
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:
156+
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:
157157

158158
```terminal
159159
npx prisma studio

content/100-getting-started/03-prisma-postgres/115-import-from-existing-database-mysql.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ If you see output like this, it means your data has been successfully exported t
133133

134134
:::note
135135

136-
You also can use [Prisma Studio](/postgres/database/tooling#viewing-and-editing-data-in-prisma-studio) and verify whether the migration was successful:
136+
You also can use [Prisma Studio](/postgres/integrations/viewing-data#viewing-and-editing-data-in-prisma-studio) and verify whether the migration was successful:
137137

138138
```terminal
139139
npx prisma studio

content/250-postgres/300-database/650-direct-connections.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ password: <none>
164164

165165
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.
166166

167-
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`**.
167+
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`.**
168168

169169
### Customizing host and port
170170

@@ -176,7 +176,7 @@ npx @prisma/ppg-tunnel --host 127.0.0.1 --port 5432
176176

177177
### Next steps
178178

179-
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).
179+
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).
180180

181181
### Security considerations
182182

content/250-postgres/1100-integrations/100-netlify.mdx renamed to content/250-postgres/350-integrations/100-netlify.mdx

File renamed without changes.
File renamed without changes.
File renamed without changes.

content/250-postgres/1100-integrations/400-mcp-server.mdx renamed to content/250-postgres/350-integrations/400-mcp-server.mdx

File renamed without changes.

content/250-postgres/300-database/700-tooling.mdx renamed to content/250-postgres/350-integrations/450-viewing-data.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: 'Tooling'
3-
metaTitle: 'Tooling'
4-
metaDescription: 'Learn about connecting directly to your database via TCP tunnel'
2+
title: 'Viewing data'
3+
metaTitle: 'Viewing data'
4+
metaDescription: 'Viewing and editing data in Prisma Postgres via Prisma Studio or other database GUIs.'
55
tocDepth: 3
66
toc: true
77
---
File renamed without changes.

content/250-postgres/1100-integrations/_category_.json renamed to content/250-postgres/350-integrations/_category_.json

File renamed without changes.

0 commit comments

Comments
 (0)