fix(client-engine-runtime): surface unmapped driver errors as user-facing P2039

[aqrln]

Closes https://linear.app/prisma-company/issue/TML-2092/customer-support-issue-qpe-crash-on-prisma-710

When a driver adapter error arrived with kind: 'postgres' (or mysql / sqlite / mssql) and the adapter did not map the underlying database error code to a more specific MappedError kind, rethrowAsUserFacing rethrew the raw DriverAdapterError unchanged.

Locally, that surfaced as PrismaClientUnknownRequestError. Worse, the query plan executor returned HTTP 500 with the real error message in the body, and Accelerate strips 500 response bodies, so end users only saw a generic P6000 with no way to diagnose the underlying problem.

This commonly happens on schema drift — e.g. an upsert() targeting a column whose unique index was dropped in the DB raises Postgres 42P10 ("there is no unique or exclusion constraint matching the ON CONFLICT specification"), which is not individually mapped by the adapter. These errors are not bugs and end users need to see the underlying DB code and message to debug.

Fix

When getErrorCode / renderErrorMessage have no specific mapping for a database-specific kind, fall back to a P2039 UserFacingError with the format Database error. Code: `X`. Message: `Y` carrying the raw originalCode / originalMessage. Consequences:

1. Locally, the error is a PrismaClientKnownRequestError(P2039, …) with the real DB details.
2. The query plan executor returns HTTP 400 with the structured error, which Accelerate forwards unchanged.
3. Truly unknown kinds (e.g. new variants from a driver-adapter ahead of the client) still fall through to assertNever so they remain visible during development.

P2010 "Raw query failed." is kept as-is for $executeRaw / $queryRaw via rethrowAsUserFacingRawError, so non-raw queries no longer claim to be raw in their error message.

P2038 and P2039 are allocated outside the public Error Reference; both are now documented in AGENTS.md and cross-referenced from the code. We need to add them to the public docs.

Tests

• New unit tests in packages/client-engine-runtime/src/user-facing-error.test.ts covering all four DB kinds, missing originalCode/originalMessage, raw-query parity (P2010 still), and a regression guard that specifically-mapped kinds (e.g. UniqueConstraintViolation → P2002) still win over the fallback.
• New functional regression test in packages/client/tests/functional/issues/unmapped-driver-error-user-facing/ that reproduces the real 42P10 upsert scenario by dropping the unique index and asserting PrismaClientKnownRequestError(P2039, …) with the raw DB details. Passes locally against js_pg, js_neon, and the QPE (--remote-executor) path.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

Summary by CodeRabbit

• New Features

  • Unmapped database errors now surface a generic user-facing error (P2039) that includes the original DB error code and message for clearer diagnostics.

• Bug Fixes

  • Raw and non-raw query errors are distinguished consistently (raw queries retain P2010), preventing misleading messages.

• Documentation

  • Clarified adapter error-handling behavior and documented fallback error codes (including P2038/P2039).

• Tests

  • Added regression and functional tests covering unmapped-driver and raw-query error formatting.

Walkthrough

Unmapped driver-adapter errors for postgres/mysql/sqlite/mssql now surface as a P2039 UserFacingError embedding the adapter originalCode/originalMessage; raw queries continue using P2010. Docs, unit tests, and a PostgreSQL functional regression test were added/updated; minor client docs comment added for P2038.

Changes

Cohort / File(s)	Summary
Documentation AGENTS.md, packages/client/src/runtime/core/engines/client/ClientEngine.ts	Documents new P2039 unmapped-driver fallback and records P2038 as the client-engine error code; adds note about raw vs non-raw messaging behavior.
Core error handling packages/client-engine-runtime/src/user-facing-error.ts	Refactors rethrow logic and helpers: centralizes raw-query error construction, uses pickErrorMessage, and throws P2039 for unmapped postgres/mysql/sqlite/mssql adapter errors while preserving driverAdapterError meta.
Unit tests (error handling) packages/client-engine-runtime/src/user-facing-error.test.ts	Adds tests for P2039 unmapped-adapter behavior (including N/A fallbacks), verifies raw queries still produce P2010, and ensures existing specific mappings are preserved.
Functional regression (Postgres) packages/client/tests/functional/issues/unmapped-driver-error-user-facing/_matrix.ts, packages/client/tests/functional/issues/unmapped-driver-error-user-facing/prisma/_schema.ts, packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts	Adds PostgreSQL-only functional test that drops a unique index to trigger a DB error (42P10) and asserts Client surfaces P2039 with original DB code/message.
Test normalization tweak packages/client/tests/functional/fulltext-search/tests.ts	Adjusts error normalization to extract the DB message from Prisma’s Code: \X`. Message: `Y`` formatted error, falling back when not matched.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 12.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: surfacing unmapped driver errors as a user-facing P2039 error code, which is the primary focus of this PR.
Description check	✅ Passed	The description is directly related to the changeset, explaining the problem, the fix, and the testing approach for surfacing unmapped driver errors as user-facing P2039.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch aqrln-nlupksywpnyp

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch aqrln-nlupksywpnyp

---

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

[github-actions]

size-limit report 📦

Path	Size
packages/client/runtime/index-browser.js	2.29 KB (0%)
packages/client/runtime/index-browser.d.ts	3.37 KB (0%)
packages/cli/build/index.js	2.54 MB (0%)
packages/client/prisma-client-0.0.0.tgz	26.83 MB (+0.02% 🔺)
packages/cli/prisma-0.0.0.tgz	13.53 MB (0%)
packages/bundle-size/da-workers-libsql/output.tgz	1.33 MB (+0.01% 🔺)
packages/bundle-size/da-workers-neon/output.tgz	1.39 MB (+0.01% 🔺)
packages/bundle-size/da-workers-pg/output.tgz	1.39 MB (+0.01% 🔺)
packages/bundle-size/da-workers-planetscale/output.tgz	1.33 MB (+0.01% 🔺)
packages/bundle-size/da-workers-d1/output.tgz	1.31 MB (+0.01% 🔺)

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/client-engine-runtime/src/user-facing-error.ts (1)

78-92: ⚠️ Potential issue | 🟠 Major

Fallback message can degrade to ``Message: undefined``` when adapter omits originalMessage`.

At Line 91 (and similarly Line 81), renderErrorMessage(error) is undefined for generic DB kinds, so missing originalMessage leaks an unusable message string.

💡 Suggested fix

 function buildRawQueryUserFacingError(error: DriverAdapterError): UserFacingError {
   return new UserFacingError(
-    `Raw query failed. Code: \`${error.cause.originalCode ?? 'N/A'}\`. Message: \`${
-      error.cause.originalMessage ?? renderErrorMessage(error)
-    }\``,
+    `Raw query failed. Code: \`${getOriginalCode(error)}\`. Message: \`${getOriginalMessage(error)}\``,
     'P2010',
     { driverAdapterError: error },
   )
 }
 
 function buildUnmappedDatabaseUserFacingError(error: DriverAdapterError): UserFacingError {
   return new UserFacingError(
-    `Database error. Code: \`${error.cause.originalCode ?? 'N/A'}\`. Message: \`${
-      error.cause.originalMessage ?? renderErrorMessage(error)
-    }\``,
+    `Database error. Code: \`${getOriginalCode(error)}\`. Message: \`${getOriginalMessage(error)}\``,
     'P2039',
     { driverAdapterError: error },
   )
 }
+
+function getOriginalCode(error: DriverAdapterError): string {
+  return error.cause.originalCode ?? 'N/A'
+}
+
+function getOriginalMessage(error: DriverAdapterError): string {
+  if (typeof error.cause.originalMessage === 'string') return error.cause.originalMessage
+  if ('message' in error.cause && typeof error.cause.message === 'string') return error.cause.message
+  return 'N/A'
+}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/client-engine-runtime/src/user-facing-error.ts` around lines 78 -
92, The templates in buildRawQueryUserFacingError and
buildUnmappedDatabaseUserFacingError can produce "Message: `undefined`" because
renderErrorMessage(error) may return undefined; update both functions to
coalesce the message fallback to a safe string (e.g., 'N/A' or 'No message
provided') instead of allowing undefined — use the combined fallback
error.cause.originalMessage ?? renderErrorMessage(error) ?? 'N/A' (or similar)
so the constructed UserFacingError message never embeds undefined.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/client-engine-runtime/src/user-facing-error.test.ts`:
- Around line 113-135: The current test "rethrowAsUserFacing falls back to N/A
when originalCode/originalMessage are missing" uses a loose prefix match on
userFacing.message so a literal "undefined" can slip through; tighten the
assertion for rethrowAsUserFacing/UserFacingError by replacing the partial match
on userFacing.message with a stricter regex that anchors the entire message and
disallows the string "undefined" (for example match ^Database error\. Code:
`N\/A`\. Message: `[^`]+`$ or alternatively add
expect(userFacing.message).not.toMatch(/undefined/)); update the assertion that
references userFacing.message in this test to use the stricter check.

---

Outside diff comments:
In `@packages/client-engine-runtime/src/user-facing-error.ts`:
- Around line 78-92: The templates in buildRawQueryUserFacingError and
buildUnmappedDatabaseUserFacingError can produce "Message: `undefined`" because
renderErrorMessage(error) may return undefined; update both functions to
coalesce the message fallback to a safe string (e.g., 'N/A' or 'No message
provided') instead of allowing undefined — use the combined fallback
error.cause.originalMessage ?? renderErrorMessage(error) ?? 'N/A' (or similar)
so the constructed UserFacingError message never embeds undefined.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 45bf4feb-9544-403a-84e5-62671b9f6cf3

📥 Commits

Reviewing files that changed from the base of the PR and between 82608c4 and c823618.

⛔ Files ignored due to path filters (1)

• packages/client/tests/functional/fulltext-search/__snapshots__/tests.ts.snap is excluded by !**/*.snap

📒 Files selected for processing (8)

• AGENTS.md
• packages/client-engine-runtime/src/user-facing-error.test.ts
• packages/client-engine-runtime/src/user-facing-error.ts
• packages/client/src/runtime/core/engines/client/ClientEngine.ts
• packages/client/tests/functional/fulltext-search/tests.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/_matrix.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/prisma/_schema.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/client-engine-runtime/src/user-facing-error.ts (1)

78-95: ⚠️ Potential issue | 🟠 Major

Fallback message construction can still emit ``Message: `undefined``` for unmapped DB errors.

When originalMessage is missing, renderErrorMessage(error) is also undefined for database-specific kinds (Line 237-241), so both P2039 and P2010 builders can generate unusable output.

Suggested fix

 function buildRawQueryUserFacingError(error: DriverAdapterError): UserFacingError {
   return new UserFacingError(
-    `Raw query failed. Code: \`${error.cause.originalCode ?? 'N/A'}\`. Message: \`${
-      error.cause.originalMessage ?? renderErrorMessage(error)
-    }\``,
+    `Raw query failed. Code: \`${error.cause.originalCode ?? 'N/A'}\`. Message: \`${resolveDatabaseMessage(error)}\``,
     'P2010',
     { driverAdapterError: error },
   )
 }
 
 function buildUnmappedDatabaseUserFacingError(error: DriverAdapterError): UserFacingError {
   return new UserFacingError(
-    `Database error. Code: \`${error.cause.originalCode ?? 'N/A'}\`. Message: \`${
-      error.cause.originalMessage ?? renderErrorMessage(error)
-    }\``,
+    `Database error. Code: \`${error.cause.originalCode ?? 'N/A'}\`. Message: \`${resolveDatabaseMessage(error)}\``,
     'P2039',
     { driverAdapterError: error },
   )
 }
+
+function resolveDatabaseMessage(error: DriverAdapterError): string {
+  if (error.cause.originalMessage) return error.cause.originalMessage
+
+  const mappedMessage = renderErrorMessage(error)
+  if (mappedMessage) return mappedMessage
+
+  const causeMessage = (error.cause as { message?: unknown }).message
+  if (typeof causeMessage === 'string' && causeMessage.length > 0) return causeMessage
+
+  return 'N/A'
+}

Also applies to: 237-241

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/client-engine-runtime/src/user-facing-error.ts` around lines 78 -
95, Both buildRawQueryUserFacingError and buildUnmappedDatabaseUserFacingError
can produce Message: `undefined` when error.cause.originalMessage and
renderErrorMessage(error) are both undefined; update both functions so the
message fallback is a safe string (e.g. use error.cause.originalMessage ??
renderErrorMessage(error) ?? 'N/A' or 'No message provided') when building the
template, ensuring the generated UserFacingError never contains `undefined`.

♻️ Duplicate comments (1)

packages/client-engine-runtime/src/user-facing-error.test.ts (1)

134-134: ⚠️ Potential issue | 🟡 Minor

Strengthen the missing-fields assertion to block ``Message: `undefined``` regressions.

Line 134 only checks a prefix, so malformed fallback output can still pass.

Suggested fix

-    expect(userFacing.message).toMatch(/^Database error\. Code: `N\/A`\. Message: `/)
+    expect(userFacing.message).toMatch(/^Database error\. Code: `N\/A`\. Message: `[^`]+`$/)
+    expect(userFacing.message).not.toContain('`undefined`')

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/client-engine-runtime/src/user-facing-error.test.ts` at line 134,
The current test only checks the prefix of userFacing.message and can miss a
fallback of "Message: `undefined`"; update the assertion in
user-facing-error.test.ts to more strictly validate the message by either
matching the full expected fallback pattern (e.g., ensure it includes a
backticked message placeholder) or add an explicit negative assertion against
/Message: `undefined`/ so the test fails if the fallback becomes the literal
"undefined"; target the existing expect(userFacing.message) assertion and
replace/augment it accordingly.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts`:
- Line 44: The DROP INDEX call in the test setup uses await
prisma.$executeRawUnsafe(`DROP INDEX "User_email_key"`) which can fail if the
index is already absent; make the setup idempotent by changing that raw SQL to
use IF EXISTS (i.e., DROP INDEX IF EXISTS ...) so reruns or partial setups don't
cause spurious failures and the regression assertion remains the only failure
point.

---

Outside diff comments:
In `@packages/client-engine-runtime/src/user-facing-error.ts`:
- Around line 78-95: Both buildRawQueryUserFacingError and
buildUnmappedDatabaseUserFacingError can produce Message: `undefined` when
error.cause.originalMessage and renderErrorMessage(error) are both undefined;
update both functions so the message fallback is a safe string (e.g. use
error.cause.originalMessage ?? renderErrorMessage(error) ?? 'N/A' or 'No message
provided') when building the template, ensuring the generated UserFacingError
never contains `undefined`.

---

Duplicate comments:
In `@packages/client-engine-runtime/src/user-facing-error.test.ts`:
- Line 134: The current test only checks the prefix of userFacing.message and
can miss a fallback of "Message: `undefined`"; update the assertion in
user-facing-error.test.ts to more strictly validate the message by either
matching the full expected fallback pattern (e.g., ensure it includes a
backticked message placeholder) or add an explicit negative assertion against
/Message: `undefined`/ so the test fails if the fallback becomes the literal
"undefined"; target the existing expect(userFacing.message) assertion and
replace/augment it accordingly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 7be822cf-1133-425a-ad31-be240715b49d

📥 Commits

Reviewing files that changed from the base of the PR and between c823618 and 50d7ed7.

⛔ Files ignored due to path filters (1)

• packages/client/tests/functional/fulltext-search/__snapshots__/tests.ts.snap is excluded by !**/*.snap

📒 Files selected for processing (8)

• AGENTS.md
• packages/client-engine-runtime/src/user-facing-error.test.ts
• packages/client-engine-runtime/src/user-facing-error.ts
• packages/client/src/runtime/core/engines/client/ClientEngine.ts
• packages/client/tests/functional/fulltext-search/tests.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/_matrix.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/prisma/_schema.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts

[coderabbitai]

Actionable comments posted: 2

♻️ Duplicate comments (1)

packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts (1)

44-44: ⚠️ Potential issue | 🟡 Minor

Make setup idempotent when dropping the unique index.

Line 44 can fail if the index is already absent, which makes this regression test flaky for reruns/retries.

Proposed fix

-      await prisma.$executeRawUnsafe(`DROP INDEX "User_email_key"`)
+      await prisma.$executeRawUnsafe(`DROP INDEX IF EXISTS "User_email_key"`)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts`
at line 44, The test setup should tolerate the index already being absent;
update the prisma.$executeRawUnsafe call that drops the unique index (the
statement `DROP INDEX "User_email_key"`) to be idempotent by either using the
DB-safe form `DROP INDEX IF EXISTS "User_email_key"` or by wrapping the
prisma.$executeRawUnsafe call in a try/catch and ignoring the specific “index
does not exist” error; modify the code that calls prisma.$executeRawUnsafe
accordingly so reruns/retries of the test won't fail.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/client-engine-runtime/src/user-facing-error.ts`:
- Around line 36-38: Replace the truthy check "if (code && message)" with
explicit undefined checks so empty strings are treated as valid mapped values;
in the UserFacingError creation path (in user-facing-error.ts) change the
condition to "if (code !== undefined && message !== undefined)" (or equivalent
explicit checks for both variables) so a mapped kind with empty-string message
or code doesn't fall through to rethrowing the raw error, then keep throwing new
UserFacingError(message, code, { driverAdapterError: error }) unchanged.

In `@packages/client/src/runtime/core/engines/client/ClientEngine.ts`:
- Around line 44-48: Remove the redundant JSDoc that describes what the constant
is; delete the comment block immediately above the CLIENT_ENGINE_ERROR constant
and leave the const CLIENT_ENGINE_ERROR = 'P2038' declaration as-is, since its
usage (where CLIENT_ENGINE_ERROR is thrown) documents its purpose and the
constant is not exported; keep no additional comment or replace it only with a
short "internal Prisma error code" inline note if you think brief context is
necessary.

---

Duplicate comments:
In
`@packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts`:
- Line 44: The test setup should tolerate the index already being absent; update
the prisma.$executeRawUnsafe call that drops the unique index (the statement
`DROP INDEX "User_email_key"`) to be idempotent by either using the DB-safe form
`DROP INDEX IF EXISTS "User_email_key"` or by wrapping the
prisma.$executeRawUnsafe call in a try/catch and ignoring the specific “index
does not exist” error; modify the code that calls prisma.$executeRawUnsafe
accordingly so reruns/retries of the test won't fail.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 54752013-1fc8-425b-861e-33a628453643

📥 Commits

Reviewing files that changed from the base of the PR and between 50d7ed7 and 4a0772a.

⛔ Files ignored due to path filters (1)

• packages/client/tests/functional/fulltext-search/__snapshots__/tests.ts.snap is excluded by !**/*.snap

📒 Files selected for processing (8)

• AGENTS.md
• packages/client-engine-runtime/src/user-facing-error.test.ts
• packages/client-engine-runtime/src/user-facing-error.ts
• packages/client/src/runtime/core/engines/client/ClientEngine.ts
• packages/client/tests/functional/fulltext-search/tests.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/_matrix.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/prisma/_schema.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts

[coderabbitai]

♻️ Duplicate comments (2)

packages/client/src/runtime/core/engines/client/ClientEngine.ts (1)

44-47: 🧹 Nitpick | 🔵 Trivial

Consider removing the JSDoc comment.

This concern was previously raised: the comment documents what the error code is used for, which is already evident from its usage at lines 129-133. Since CLIENT_ENGINE_ERROR is not exported, it should not have a JSDoc comment per coding guidelines. As per coding guidelines, comments should explain why (context, decisions) rather than what, and documentation comments are for exported items.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/client/src/runtime/core/engines/client/ClientEngine.ts` around lines
44 - 47, Remove the redundant JSDoc that describes the Prisma error code for
CLIENT_ENGINE_ERROR; since CLIENT_ENGINE_ERROR is not exported and the comment
only restates what the constant does, delete the JSDoc block above the
CLIENT_ENGINE_ERROR declaration in ClientEngine.ts and leave a brief inline
comment only if needed for rationale (not what) per guidelines.

packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts (1)

44-44: ⚠️ Potential issue | 🟡 Minor

Make the index drop idempotent in test setup.

Line 44 can fail on reruns if the index is already absent, which makes the setup flaky and can hide the actual regression signal.

Proposed fix

-      await prisma.$executeRawUnsafe(`DROP INDEX "User_email_key"`)
+      await prisma.$executeRawUnsafe(`DROP INDEX IF EXISTS "User_email_key"`)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts`
at line 44, The test setup currently calls prisma.$executeRawUnsafe(`DROP INDEX
"User_email_key"`) which fails if the index is already absent; make this
idempotent by either using a conditional drop (e.g. `DROP INDEX IF EXISTS
"User_email_key"`) in the prisma.$executeRawUnsafe call or wrapping the existing
prisma.$executeRawUnsafe(...) in a try/catch that ignores the specific “index
does not exist” error; update the call site (the prisma.$executeRawUnsafe
invocation) accordingly so rerunning the test won’t error.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@packages/client/src/runtime/core/engines/client/ClientEngine.ts`:
- Around line 44-47: Remove the redundant JSDoc that describes the Prisma error
code for CLIENT_ENGINE_ERROR; since CLIENT_ENGINE_ERROR is not exported and the
comment only restates what the constant does, delete the JSDoc block above the
CLIENT_ENGINE_ERROR declaration in ClientEngine.ts and leave a brief inline
comment only if needed for rationale (not what) per guidelines.

In
`@packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts`:
- Line 44: The test setup currently calls prisma.$executeRawUnsafe(`DROP INDEX
"User_email_key"`) which fails if the index is already absent; make this
idempotent by either using a conditional drop (e.g. `DROP INDEX IF EXISTS
"User_email_key"`) in the prisma.$executeRawUnsafe call or wrapping the existing
prisma.$executeRawUnsafe(...) in a try/catch that ignores the specific “index
does not exist” error; update the call site (the prisma.$executeRawUnsafe
invocation) accordingly so rerunning the test won’t error.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 541a4116-1613-4eb2-ab86-bab59638f461

📥 Commits

Reviewing files that changed from the base of the PR and between 4a0772a and 7922c6f.

⛔ Files ignored due to path filters (1)

• packages/client/tests/functional/fulltext-search/__snapshots__/tests.ts.snap is excluded by !**/*.snap

📒 Files selected for processing (8)

• AGENTS.md
• packages/client-engine-runtime/src/user-facing-error.test.ts
• packages/client-engine-runtime/src/user-facing-error.ts
• packages/client/src/runtime/core/engines/client/ClientEngine.ts
• packages/client/tests/functional/fulltext-search/tests.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/_matrix.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/prisma/_schema.ts
• packages/client/tests/functional/issues/unmapped-driver-error-user-facing/test.ts