Fix SQL schema selector execution

Fix schema-aware SQL execution, linting, and Studio navigation; includes a minor changeset for @prisma/studio-core.

Author: sorenbs

.changeset/silver-schema-sql.md

@@ -0,0 +1,5 @@
+---
+"@prisma/studio-core": minor
+---
+
+Fix schema-aware SQL execution, linting, and Studio navigation so SQL queries and diagnostics resolve unqualified identifiers against the selected schema instead of always relying on the adapter default schema.

Architecture/navigation-url-state.md

@@ -112,6 +112,9 @@ Use two patterns only:
 - Imperative updates: `setViewParam`, `setSchemaParam`, `setTableParam`, `setStreamParam`, etc.
 
 On schema switch, code MUST also resolve and set a valid table for that schema (current behavior in `Navigation.SchemaSelector`).
+Database view links in the Studio sidebar (`schema`, `queries`, `console`, and
+`sql`) MUST preserve the active `schema` URL param so switching views does not
+silently fall back to the adapter default schema.
 
 ## Context Boundary
 

Architecture/sql-editor-intelligence.md

@@ -51,6 +51,9 @@ This architecture governs:
   - stale responses MUST be discarded via request id check
 - Diagnostics MUST be clamped to document bounds before returning to CodeMirror.
 - Empty SQL MUST short-circuit with no lint request.
+- SQL editor language configuration and lint requests MUST use the active URL
+  schema as the default schema so completions and diagnostics match the schema
+  selector.
 - Table-level SQL filter pills MAY reuse the same adapter `sqlLint` transport, but they MUST wrap raw `WHERE` fragments in a full `SELECT ... WHERE ...` statement before linting.
 - SQL filter-pill linting MUST run asynchronously in the background and MUST NOT block the initial filter apply interaction.
 - Table-level SQL filter-pill lint diagnostics are advisory UI state only and MUST NOT mutate the already-applied URL filter after the pill has been saved.
@@ -61,6 +64,8 @@ This architecture governs:
   - existing `customHeaders`
   - existing `customPayload`
 - Procedure name for linting is `sql-lint`.
+- Lint request payloads MAY include `schema`; when present, the backend MUST
+  plan unqualified identifiers against that schema.
 - New SQL-editor surfaces MUST NOT bypass BFF auth propagation.
 - Executor contract:
   - `Executor` MAY expose `lintSql(details, options)` as an optimized lint transport.
@@ -79,6 +84,7 @@ This architecture governs:
   - `statement_timeout = 1000ms`
   - `lock_timeout = 100ms`
   - `idle_in_transaction_session_timeout = 1000ms`
+- transaction-local `search_path` when a selected schema is provided
 
 On Postgres errors, diagnostics MUST include mapped position and SQLSTATE when available. Timeout diagnostics (`57014`) MUST be rewritten to a user-facing lint-timeout message.
 For multi-statement SQL text, diagnostics MUST map statement-relative positions back to full-editor offsets.

Architecture/sql-view.md

@@ -53,6 +53,11 @@ SQL result visualization is governed by:
 - SQL execution target is cursor-aware:
   - single-statement editor text: execute that statement
   - multi-statement editor text: execute the top-level statement containing the cursor
+- SQL execution MUST pass the active URL schema to `adapter.raw(...)` so
+  unqualified identifiers resolve against the schema selected in Studio.
+- PostgreSQL raw execution MUST apply the active schema through a
+  transaction-local `search_path` and MUST NOT leak schema changes across
+  requests or connections.
 - The grid renders all rows returned by that execution.
 - "row(s) returned in Xms" MUST report client-observed request duration from
   the SQL request transport (BFF request timing) when available; it MUST NOT
@@ -94,6 +99,7 @@ SQL result visualization is governed by:
 Changes to SQL view MUST include tests for:
 
 - query execution success and cancellation behavior
+- query execution with an active non-public schema
 - read-only grid rendering (pin control present, sorting controls disabled)
 - absence of history UI
 - absence of pagination controls in SQL result grid

FEATURES.md

@@ -208,6 +208,7 @@ Matching substrings are highlighted in the grid, and timeout errors explain that
 
 The SQL view uses a full CodeMirror editor with dialect-aware syntax highlighting and schema-aware autocomplete for schemas, tables, and columns.
 Autocomplete is built from live introspection metadata, so suggestions track the current database structure without manual refresh workflows.
+The active schema selector is also used as the default SQL namespace, so unqualified queries like `select * from order_items` run and lint against the selected schema instead of always resolving through `public`.
 PostgreSQL, MySQL, and SQLite linting runs asynchronously through guarded parse/plan `EXPLAIN` paths and shows inline diagnostics while preserving the normal run/cancel query flow.
 The same lint transport also validates saved table-level SQL filter pills in the background, so Studio reuses one dialect-aware SQL validation path for both the SQL editor and advanced inline table filters.
 Keyboard execution supports `Cmd/Ctrl+Enter`, and in multi-statement scripts it runs only the top-level statement at the current cursor.

README.md

@@ -363,6 +363,7 @@ type StudioBFFRequest =
   | {
       procedure: "query";
       query: Query;
+      schema?: string;
       customPayload?: Record<string, unknown>;
     }
   | {
@@ -378,6 +379,7 @@ type StudioBFFRequest =
   | {
       procedure: "sql-lint";
       sql: string;
+      schema?: string;
       schemaVersion?: string;
       customPayload?: Record<string, unknown>;
     }
@@ -419,10 +421,10 @@ type QueryInsightsResponse =
 
 ### Procedure Semantics
 
-- `query`: execute one SQL statement. This is required for every Studio adapter.
+- `query`: execute one SQL statement. This is required for every Studio adapter. Requests may include `schema`; when present, use it as the default namespace for unqualified identifiers.
 - `sequence`: execute exactly two queries in order. This is used by MySQL write flows that update first and refetch second.
 - `transaction`: execute an ordered list of queries inside one database transaction. This is the contract addition that enables atomic staged multi-row saves from the table editor.
-- `sql-lint`: return parse/plan diagnostics for the SQL editor and SQL-backed filter pills.
+- `sql-lint`: return parse/plan diagnostics for the SQL editor and SQL-backed filter pills. Requests may include `schema`; diagnostics should plan unqualified identifiers against that selected schema.
 - `query-insights`: return a live query snapshot for the optional `Queries` view.
 
 For `sequence`, the second query should only run if the first one succeeds. For `transaction`, the response result array must stay in the same order as `body.queries`.
@@ -469,7 +471,9 @@ export async function handleStudioBff(request: Request): Promise<Response> {
   }
 
   if (payload.procedure === "query") {
-    const [error, result] = await executor.execute(payload.query);
+    const [error, result] = await executor.execute(payload.query, {
+      schema: payload.schema,
+    });
     return Response.json([error ? serializeError(error) : null, result]);
   }
 
@@ -513,6 +517,7 @@ export async function handleStudioBff(request: Request): Promise<Response> {
     }
 
     const [error, result] = await executor.lintSql({
+      schema: payload.schema,
       schemaVersion: payload.schemaVersion,
       sql: payload.sql,
     });

data/adapter.ts

@@ -380,6 +380,10 @@ export interface AdapterQueryResult {
 }
 
 export interface AdapterRawDetails {
+  /**
+   * Schema to use as the default namespace for unqualified identifiers.
+   */
+  schema?: string;
   sql: string;
 }
 
@@ -400,6 +404,10 @@ export interface AdapterSqlSchemaResult {
 }
 
 export interface AdapterSqlLintDetails {
+  /**
+   * Schema to use as the default namespace for unqualified identifiers.
+   */
+  schema?: string;
   schemaVersion?: string;
   sql: string;
 }

data/bff/bff-client.test.ts

@@ -74,6 +74,27 @@ describe("bff/bff-client", () => {
         expect(response).toStrictEqual([null, results]);
       });
 
+      it("should send selected schema context when provided", async () => {
+        fetchFn.mockResolvedValueOnce(
+          new Response(JSON.stringify([null, results])),
+        );
+
+        const response = await client.execute(query, {
+          schema: "test_app",
+        });
+        const latestFetchCall = fetchFn.mock.calls.at(-1);
+
+        expect(latestFetchCall?.[0]).toBe(url);
+        expect(JSON.parse(latestFetchCall?.[1]?.body as string)).toStrictEqual({
+          customPayload,
+          procedure: "query",
+          query,
+          schema: "test_app",
+        });
+
+        expect(response).toStrictEqual([null, results]);
+      });
+
       it("should return (not throw) an error if the request fails", async () => {
         const error = "Internal server error";
         fetchFn.mockResolvedValueOnce(new Response(error, { status: 500 }));
@@ -564,6 +585,7 @@ describe("bff/bff-client", () => {
 
     describe("lintSql", () => {
       const details = {
+        schema: "test_app",
         schemaVersion: "schema-abc123",
         sql: "select * from users",
       };
@@ -605,6 +627,7 @@ describe("bff/bff-client", () => {
             expect(JSON.parse(value as string)).toStrictEqual({
               customPayload,
               procedure: "sql-lint",
+              schema: "test_app",
               schemaVersion: "schema-abc123",
               sql: "select * from users",
             });

data/bff/bff-client.ts

@@ -281,6 +281,7 @@ export interface StudioBFFQueryRequest {
   customPayload?: Record<string, unknown>;
   procedure: "query";
   query: Query<unknown>;
+  schema?: string;
 }
 
 export interface StudioBFFSequenceRequest {
@@ -296,6 +297,7 @@ export interface StudioBFFTransactionRequest {
 }
 
 export interface StudioBFFSqlLintDetails {
+  schema?: string;
   schemaVersion?: string;
   sql: string;
 }
@@ -308,6 +310,7 @@ export interface StudioBFFSqlLintResult {
 export interface StudioBFFSqlLintRequest {
   customPayload?: Record<string, unknown>;
   procedure: "sql-lint";
+  schema?: string;
   schemaVersion?: string;
   sql: string;
 }
@@ -335,6 +338,7 @@ export function createStudioBFFClient(
             customPayload,
             procedure: "query",
             query,
+            schema: options?.schema,
           } satisfies StudioBFFQueryRequest),
           headers: {
             Accept: "application/json",
@@ -516,6 +520,7 @@ export function createStudioBFFClient(
           body: JSON.stringify({
             customPayload,
             procedure: "sql-lint",
+            schema: details.schema,
             schemaVersion: details.schemaVersion,
             sql: details.sql,
           } satisfies StudioBFFSqlLintRequest),

data/executor.ts

@@ -36,9 +36,17 @@ export interface SequenceExecutor extends Executor {
 
 export interface ExecuteOptions {
   abortSignal?: AbortSignal;
+  /**
+   * Schema to use as the default namespace for unqualified identifiers.
+   */
+  schema?: string;
 }
 
 export interface SqlLintDetails {
+  /**
+   * Schema to use as the default namespace for unqualified identifiers.
+   */
+  schema?: string;
   schemaVersion?: string;
   sql: string;
 }