Skip to content

Commit 1e78222

Browse files
committed
fix internal links
1 parent 7a9d57e commit 1e78222

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ pg_restore \
153153

154154
Once the command completes execution, you will have successfully imported the data from your 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/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:
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/tooling#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 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`**.
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/tooling).
180180

181181
### Security considerations
182182

static/_redirects

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -542,7 +542,7 @@
542542
/postgres/connection-pooling /docs/postgres/database/connection-pooling
543543
/postgres/backups /docs/postgres/database/backups
544544
/postgres/tcp-tunnel /docs/postgres/database/tcp-tunnel
545-
/postgres/tooling /docs/postgres/database/tooling
545+
/postgres/tooling /docs/postgres/integrations/tooling
546546
/postgres/caching /docs/postgres/database/caching
547547

548548
/optimize/recommendations/excessive-number-of-rows-returned /docs/postgres/query-optimization/recommendations/excessive-number-of-rows-returned
@@ -619,7 +619,7 @@
619619
/postgres/connection-pooling* /docs/postgres/database/connection-pooling
620620
/postgres/backups* /docs/postgres/database/backups
621621
/postgres/tcp-tunnel* /docs/postgres/database/tcp-tunnel
622-
/postgres/tooling* /docs/postgres/database/tooling
622+
/postgres/tooling* /docs/postgres/integrations/tooling
623623
/postgres/api-reference* /docs/postgres/database/api-reference
624624

625625
/optimize/recommendations/* /docs/postgres/query-optimization/recommendations
@@ -633,7 +633,7 @@
633633
/postgres/more/known-limitations /docs/postgres/introduction/overview
634634
/postgres/integrations/vscode-extension* /postgres/integrations/vscode:splat
635635

636-
/postgres/database/tooling /docs/postgres/integrations/tooling
636+
/postgres/integrations/tooling /docs/postgres/integrations/tooling
637637

638638

639639

0 commit comments

Comments
 (0)