docs(ppg): updates

Author: mhartington

content/250-postgres/100-introduction/220-npx-create-db.mdx

@@ -96,37 +96,28 @@ Here is an example output:
 ┌  🚀 Creating a Prisma Postgres database
 │
 │  Provisioning a temporary database in us-east-1...
-│
 │  It will be automatically deleted in 24 hours, but you can claim it.
-│
 ◇  Database created successfully!
 │
-●  Connect to your database →
-│
-│    Use this connection string optimized for Prisma ORM:
-│    prisma+postgres://accelerate.prisma-data.net/?api_key=...
-│
-│    Use this connection string for everything else:
+●  Database Connection
+│    Connection String:
 │    postgresql://<username>:<password>@db.prisma.io:5432/postgres
 │
 ◆  Claim your database →
-│
-│    Want to keep your database? Claim for free:
+│    Keep your database for free:
 │    https://create-db.prisma.io?projectID=proj_...
 └
 ```
 
 
-Once you have the output, take the **Prisma ORM-optimized connection string** (`prisma+postgres://...`) and add it to your `.env` file as `DATABASE_URL`:
+Once you have the output, take the connection string and add it to your `.env` file as `DATABASE_URL`:
 
 ```env
-DATABASE_URL="prisma+postgres://accelerate.prisma-data.net/?api_key=..."
+DATABASE_URL="postgresql://<username>:<password>@db.prisma.io:5432/postgres"
 ```
 
 You can now follow the [Prisma Postgres quickstart guide](/getting-started/prisma-orm/quickstart/prisma-postgres) to connect your Prisma project to this database.
 
-If you're using other tools or libraries, use the **standard PostgreSQL connection string** (`postgresql://...`) with any PostgreSQL-compatible client, such as `psql`, `pgAdmin`, `node-postgres`, or an ORM of your choice. Detailed instructions are available in the guide for [connecting via direct PostgreSQL connection string](/postgres/database/direct-connections).
-
 
 ## Claiming your database
 
@@ -163,12 +154,12 @@ When you claim a database:
 
 Here are the CLI flags for the `npx create-db` command:
 
-| Flag        | Shorthand | Description                                                                                  |
-|---------------|-----------|----------------------------------------------------------------------------------------------|
-| `--region`    | `-r`      | Specify a region. <br /> **Available regions:** `ap-southeast-1`, `ap-northeast-1`, `eu-central-1`, `eu-west-3`, `us-east-1`, `us-west-1` |
-| `--interactive` | `-i`    | Run in interactive mode (select region from a list).                                         |
-| `--json` | `-j`    | Output machine-readable JSON and exit.                                         |
-| `--help`      | `-h`      | Show this help message.                                                                      |
+| Flag            | Shorthand | Description                                                                                                                               |
+|-----------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| `--region`      | `-r`      | Specify a region. <br /> **Available regions:** `ap-southeast-1`, `ap-northeast-1`, `eu-central-1`, `eu-west-3`, `us-east-1`, `us-west-1` |
+| `--interactive` | `-i`      | Run in interactive mode (select region from a list).                                                                                      |
+| `--json`        | `-j`      | Output machine-readable JSON and exit.                                                                                                    |
+| `--help`        | `-h`      | Show this help message.                                                                                                                   |
 
 
 To view all CLI options use the `--help` or `-h` flag:

content/250-postgres/1200-more/1000-faq.mdx

@@ -29,11 +29,8 @@ If you previously signed up using GitHub and want to switch to email and passwor
 3. Test Your Login
     - Log out and try logging in with your email and the password you just created.
 
-:::note
-
 If you encounter any issues, please contact our support team for help linking your accounts.
 
-:::
 
 ### VS Code does not recognize the `$extends` method
 

content/250-postgres/1200-more/900-troubleshooting.mdx

@@ -33,28 +33,6 @@ npx prisma@latest init --db
 
 This ensures that you're using the most up-to-date CLI, preventing issues with outdated command syntax.
 
-##  Warning: In production, we recommend using `prisma generate --no-engine`
-
-### Problem
-
-You're seeing the following error in your logs:
-
-```
-prisma:warn: In production, we recommend using 'prisma generate --no-engine'
-```
-
-### Cause
-
-Prisma ORM by default uses a [query engine](/orm/overview/) binary that's deployed as part of the `@prisma/client` package. However, with Prisma Postgres, this is not needed.
-
-### Solution
-
-To remove this warning and generate Prisma Client without the query engine, you can run the following command:
-
-```
-npx prisma generate --no-engine
-```
-
 ## Workspace plan limit reached when running `prisma init --db`
 
 ### Problem

content/250-postgres/300-database/400-connection-pooling.mdx

@@ -18,26 +18,13 @@ For Prisma Postgres, the connection limit depends on the plan you have signed up
 |---------------------------|------|---------|-----|----------|
 | Connection Limit (Pooled) | 10   | 100     | 500 | 1000     |
 
-:::note
-For the **Starter plan**, this is often sufficient for most workloads, but if you're expecting high traffic or intensive compute operations, you may want to [increase this limit](#configuring-the-connection-pool-size).
-:::
-
 You can compare plans on the [Prisma pricing page](https://www.prisma.io/pricing).
 
 
-### Configuring the connection pool size
-
-For Prisma Postgres, the connection limit is managed automatically for you.
-
-If you're **not using Prisma Postgres**, you can configure the connection pool size for Prisma ORM by specifying it [in the connection string](/orm/prisma-client/setup-and-configuration/databases-connections/connection-pool#setting-the-connection-pool-size).
-
-If you're using Prisma Accelerate with your own database, you can configure the connection pool size through the `Connection limit` setting in your project on the [Accelerate setup page](/accelerate/getting-started).
-
-### Configuring the connection pool timeout
+### Connection pool timeout
 
 The connection pool timeout is the maximum number of seconds that a query will block while waiting for a connection from Prisma Postgres's internal connection pool. This occurs if the number of concurrent requests exceeds the connection limit, resulting in queueing of additional requests until a free connection becomes available. An exception is thrown if a free connection does not become available within the pool timeout. The connection pool timeout can be disabled by setting the value to 0.
 
-Similar to the connection pool size, you may also configure the connection pool timeout via the _database connection string_. To adjust this value, you may add the `pool_timeout` parameter to the database connection string.
 
 For example:
 

content/250-postgres/300-database/550-local-development.mdx

@@ -10,19 +10,13 @@ sidebar_class_name: preview-badge
 
 [Prisma Postgres](/postgres) is a production-grade, cloud-native database and is ideal for staging and production environments. For rapid iteration and isolated testing, you can run a _local_ Prisma Postgres instance (powered by [PGlite](https://pglite.dev)) via the `prisma dev` command. This page explains how to install and launch a local Prisma Postgres database.
 
-:::note
-
 Local Prisma Postgres is in [Preview](/orm/more/releases#preview) and is being actively developed.
 
-:::
-
 ## Setting up local development for Prisma Postgres
 
 Follow these steps to set up local Prisma Postgres for development.
 
-:::note
-Please ensure you're running Node.js 20 or later, as it's required for local Prisma Postgres.
-:::
+Node.js v20 or later is required for local Prisma Postgres
 
 ### 1. Launching local Prisma Postgres
 
@@ -56,16 +50,6 @@ If you want to connect via Prisma ORM, hit <kbd>h</kbd> on your keyboard, copy t
 DATABASE_URL="prisma+postgres://localhost:51213/?api_key=__API_KEY__"
 ```
 
-The `DATABASE_URL` is a connection string that Prisma uses to connect to the local Prisma Postgres server and is compatible with the [Prisma Postgres extension](https://www.npmjs.com/package/@prisma/extension-accelerate):
-
-```ts
-import { withAccelerate } from '@prisma/extension-accelerate'
-
-const prisma = new PrismaClient().$extends(withAccelerate())
-```
-
-This ensures no additional code changes are needed when switching from local Prisma Postgres to Prisma Postgres in production.
-
 Keep the local Prisma Postgres server running in the background while you work on your application. 
 
 ### 2. Applying migrations and seeding data

content/250-postgres/300-database/750-serverless-driver.mdx

@@ -9,6 +9,12 @@ sidebar_class_name: early-access-badge
 
 The serverless driver for Prisma Postgres is a lightweight and minimal client library that can talk to Prisma Postgres using raw SQL. You can use it via the [`@prisma/ppg`](https://github.com/prisma/ppg-client/tree/main) npm package.
 
+:::warning
+
+The Prisma Postgres serverless driver is currently in [Early Access](/orm/more/releases#early-access) and not yet recommended for production scenarios.
+
+:::
+
 ## Installation
 
 Install the serverless driver via npm:
@@ -32,7 +38,7 @@ type Post = {
   authorId: number | null;
 }
 
-const sql = ppg(YOUR_DATABASE_URL);
+const sql = ppg("prisma+postgres://accelerate.prisma-data.net/?api_key=...");
 
 const authorId = 1;
 const posts = await sql<Post>`SELECT * FROM "Post" WHERE "authorId" = ${authorId}`;
@@ -97,7 +103,7 @@ type User = {
   email: string
 }
 
-const sql = ppg(YOUR_DATABASE_URL);
+const sql = ppg("prisma+postgres://accelerate.prisma-data.net/?api_key=...");
 
 const posts: Post[] = await sql<Post>`SELECT * FROM "Post"`
 
@@ -132,7 +138,7 @@ The `query` function it exposes:
 import { Client } from "@prisma/ppg";
 
 const client = new Client({
-  connectionString: YOUR_DATABASE_URL,
+  connectionString: "prisma+postgres://accelerate.prisma-data.net/?api_key=...",
 });
 
 const posts = await client.query('SELECT * FROM "Post" WHERE "authorId" = $1', [1]);

content/250-postgres/50-getting-started/index.mdx

@@ -16,15 +16,13 @@ npx prisma init --db
 
 After running this command, the terminal will guide you with next steps. Follow [this page](/getting-started/prisma-postgres/from-the-cli) to complete the setup for your first Prisma Postgres project.
 
-:::note
 If you need a database quickly for testing, or want to try out Prisma Postgres, you can run the following command to spin up a temporary 24-hour database: 
 
 ```terminal
 npx create-db@latest
 ```
 
 You can learn more about `npx create-db` in [the dedicated documentation](/postgres/introduction/npx-create-db).
-:::
 
 ## Prisma ORM
 
@@ -40,16 +38,7 @@ If you are looking to explore Prisma Postgres in a fullstack project, check out
 
 ## Connect via any database library / tool
 
-You can access Prisma Postgres with any ORM or database tool of your choice via [direct TCP connections](/postgres/database/direct-connections).
-
-In order to get a direct TCP connection string, you need to:
-1. Navigate to your active Prisma Postgres instance.
-1. Click the **API Keys** tab in the project's sidenav.
-1. Click the **Create API key** button.
-1. In the popup, provide a **Name** for the API key and click **Create**.
-1. Copy the connection string starting with `postgres://`, this is your direct connection string.
-
-Once you have the connection string, you can follow the setup docs for PostgreSQL of any ORM or database tool:
+You can access Prisma Postgres with any ORM or database tool of your choice. Once you have the connection string, you can follow the setup docs for PostgreSQL of any ORM or database tool:
 
 - [Drizzle ORM](https://orm.drizzle.team/docs/get-started/postgresql-new)
 - [Kysely](https://kysely.dev/docs/getting-started)