From 5503b1483012bd3f632c1f9e66314a525deac9f3 Mon Sep 17 00:00:00 2001 From: Ankur Datta <64993082+ankur-arch@users.noreply.github.com> Date: Tue, 25 Nov 2025 15:46:51 +0600 Subject: [PATCH] fix: add callout to resolve studio error --- .../200-orm/400-tools/06-prisma-studio.mdx | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/content/200-orm/400-tools/06-prisma-studio.mdx b/content/200-orm/400-tools/06-prisma-studio.mdx index 6a3592f826..bff45829c7 100644 --- a/content/200-orm/400-tools/06-prisma-studio.mdx +++ b/content/200-orm/400-tools/06-prisma-studio.mdx @@ -172,6 +172,32 @@ Support for CockroachDB and MongoDB is not currently available but may be added ## Troubleshooting +### PostgreSQL: "unrecognized configuration parameter 'schema'" error + +When connecting to PostgreSQL databases, you may encounter this error if your connection string includes the `schema` query parameter: + +```terminal wrap +unrecognized configuration parameter "schema" +``` + +This happens because the new Studio is standalone and passes your connection URL directly to the PostgreSQL driver without any processing. The URL you provide—whether via `prisma.config.ts` or the `--url` flag—must be a valid PostgreSQL connection string that only uses [standard PostgreSQL connection parameters](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-PARAMKEYWORDS). + +The `schema` parameter was a custom Prisma ORM parameter that worked in v6 and earlier, but PostgreSQL itself doesn't recognize it. + +To resolve this issue, use the standard `search_path` parameter instead: + +```terminal +# ❌ This will cause an error +postgresql://user:password@host:port/database?schema=my_schema + +# ✅ Use this instead +postgresql://user:password@host:port/database?options=-c%20search_path%3Dmy_schema +``` + +Alternatively, you can remove the schema parameter entirely if you're using the default `public` schema, as PostgreSQL defaults to it automatically. + +For more details, see the related [GitHub issue](https://github.com/prisma/studio/issues/1363#issuecomment-3561040763). + ### Terminal: Failed to run script / Error in Prisma Client request Caching issues may cause Prisma Studio to use an older version of the query engine. You may see the following error: