update prisma postgres example

[AmanVarshney01]

Summary by CodeRabbit

• Documentation

  • Completely rewrote the getting-started guide with a streamlined quick-start flow, replacing verbose multi-step setup with concise instructions and minimal CLI commands.

• Chores

  • Updated Prisma, PostgreSQL adapters, and development dependencies to latest versions for improved compatibility.
  • Refactored example codebase with simplified, focused implementation demonstrating core database operations.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR modernizes the Prisma Postgres example by migrating from the Accelerate extension to the PostgreSQL adapter pattern. It updates dependencies, simplifies documentation, removes separate caching and query examples, and consolidates functionality into a single entry point demonstrating core CRUD operations.

Changes

Cohort / File(s)	Summary
Documentation databases/prisma-postgres/README.md	Simplified getting-started guide; replaced detailed Accelerate provisioning workflow with concise adapter-based setup instructions. Removed intermediate steps like Prisma Studio exploration and SWR/TTL caching explanations.
Configuration databases/prisma-postgres/package.json	Updated package name from hello-prisma to prisma-postgres-example; replaced scripts (removed queries, caching; added dev entry point); updated Prisma and tooling dependencies to use adapter-pg pattern and newer versions (Prisma 7.1.0, TypeScript 5.8.3, tsx 4.19.4).
Example Code — Removed databases/prisma-postgres/src/caching.ts, databases/prisma-postgres/src/queries.ts	Deleted standalone caching example (Accelerate-based cached queries) and seed/queries script; functionality consolidated into new index.ts.
Example Code — Added databases/prisma-postgres/src/index.ts	New entry point demonstrating PostgreSQL adapter initialization, basic CRUD operations (create user with post, query published posts, update post, disconnect), and error handling.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Key areas for review:
  • Verify PostgreSQL adapter configuration and DATABASE_URL environment variable handling in new index.ts
  • Confirm dependency version changes (Prisma, adapter-pg, TypeScript, tsx) are compatible and necessary
  • Validate that consolidated example in index.ts covers the core functionality previously split across caching.ts and queries.ts
  • Check that README accurately reflects the new simplified setup flow

Possibly related PRs

• Update misc examples with prisma.config.ts and adapter #8362: Also migrates examples from Accelerate extension to adapter-based setup with PostgreSQL adapter usage.
• Update Bun & Deno examples #8343: Modifies Prisma client initialization and environment-based connection setup using adapter-pg and DATABASE_URL pattern.
• Revert "update cockroachdb, postgresql-supabase, prisma-postgres exam… #8384: Overlaps on databases/prisma-postgres files; changes Prisma client initialization and configuration patterns.

Pre-merge checks

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title check	❓ Inconclusive	The title 'update prisma postgres example' is vague and generic, using non-descriptive terms that don't convey the specific nature of the substantial refactoring performed.	Consider a more specific title that captures the main intent, such as 'Simplify Prisma Postgres example with streamlined setup' or 'Refactor Prisma Postgres example to use adapter pattern.'

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

databases/prisma-postgres/src/index.ts (1)

34-35: Add safety check for array access.

Direct access to user.posts[0] assumes the posts array has at least one element. While this should be true given the preceding create operation, defensive coding is recommended.

Apply this diff:

   // Update a post
   const updatedPost = await prisma.post.update({
-    where: { id: user.posts[0].id },
+    where: { id: user.posts[0]?.id },
     data: { title: "Hello from Prisma Postgres! (updated)" },
   });

Or add an explicit check:

   // Update a post
+  if (user.posts.length === 0) {
+    throw new Error("No posts found for user");
+  }
   const updatedPost = await prisma.post.update({
     where: { id: user.posts[0].id },
     data: { title: "Hello from Prisma Postgres! (updated)" },
   });

databases/prisma-postgres/README.md (1)

19-50: Consider mentioning npm/pnpm alternatives.

The README assumes Bun is available. While Bun is fast and modern, consider mentioning npm or pnpm alternatives for broader accessibility, especially since the example works with any package manager.

Optional addition after line 19:

 cd prisma-postgres
 bun install
+# Or use npm install / pnpm install

And after line 50:

```diff
 bun run dev
+# Or use npm run dev / pnpm run dev

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used**: Path: .coderabbit.yaml

**Review profile**: CHILL

**Plan**: Pro

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between e725bc152232a61acc8d26a22f0e547eb9b39f7d and aa2ea8f013917f2ef7f904e88c7bbf0c5e8dd924.

</details>

<details>
<summary>📒 Files selected for processing (5)</summary>

* `databases/prisma-postgres/README.md` (1 hunks)
* `databases/prisma-postgres/package.json` (1 hunks)
* `databases/prisma-postgres/src/caching.ts` (0 hunks)
* `databases/prisma-postgres/src/index.ts` (1 hunks)
* `databases/prisma-postgres/src/queries.ts` (0 hunks)

</details>

<details>
<summary>💤 Files with no reviewable changes (2)</summary>

* databases/prisma-postgres/src/queries.ts
* databases/prisma-postgres/src/caching.ts

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🧬 Code graph analysis (1)</summary>

<details>
<summary>databases/prisma-postgres/src/index.ts (1)</summary><blockquote>

<details>
<summary>orm/prisma-mocking-javascript/client.js (1)</summary>

* `adapter` (4-4)

</details>

</blockquote></details>

</details>

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (16)</summary>

* GitHub Check: test (orm/nest-graphql)
* GitHub Check: test (orm/betterauth-nextjs)
* GitHub Check: test (orm/betterauth-astro)
* GitHub Check: test (orm/grpc)
* GitHub Check: test (orm/nextjs)
* GitHub Check: test (orm/authjs-nextjs)
* GitHub Check: test (orm/ai-sdk-nextjs)
* GitHub Check: test (orm/clerk-nextjs)
* GitHub Check: test (orm/clerk-astro)
* GitHub Check: test (orm/hapi-graphql)
* GitHub Check: test (orm/astro)
* GitHub Check: test (orm/cloudflare-workers)
* GitHub Check: test (orm/nest-graphql-sdl-first)
* GitHub Check: test (orm/nuxt)
* GitHub Check: test (orm/sveltekit)
* GitHub Check: test (orm/solid-start)

</details>

<details>
<summary>🔇 Additional comments (5)</summary><blockquote>

<details>
<summary>databases/prisma-postgres/src/index.ts (5)</summary><blockquote>

`8-24`: **LGTM!**

The user creation with nested post creation demonstrates Prisma's relation handling correctly. Using `Date.now()` for email uniqueness is appropriate for an example.

---

`26-31`: **LGTM!**

The query correctly demonstrates filtering and including relations.

---

`41-43`: **LGTM!**

The error handling pattern with `catch` and `finally` ensures proper cleanup via `$disconnect()` regardless of success or failure.

---

`5-6`: **The `connectionString` parameter is correct for PrismaPg.**

The PrismaPg constructor API accepts `connectionString` as the parameter name, matching the official Prisma documentation. The code at lines 5-6 follows the correct API usage.

However, adding validation for the `DATABASE_URL` environment variable is a reasonable defensive coding practice to provide clearer error messages if the variable is missing:

```diff
+if (!process.env.DATABASE_URL) {
+  throw new Error("DATABASE_URL environment variable is not defined");
+}
+
 const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL });
 const prisma = new PrismaClient({ adapter });

Likely an incorrect or invalid review comment.

---

2-2: This import path is intentional but part of a non-standard Prisma configuration.

The schema uses a custom generator with provider = "prisma-client" and output = "./generated", making the import path ../prisma/generated/client correct for this setup. However, the prisma/generated directory doesn't exist yet—it must be created by running prisma generate first. Additionally, since @prisma/client is already listed as a dependency, consider using the standard import path instead:

-import { PrismaClient } from "../prisma/generated/client";
+import { PrismaClient } from "@prisma/client";

This custom generator setup is unconventional and may cause issues if the generated directory is not present or if the custom provider is not properly configured.