fix(adapters): handle P2025 errors without importing Prisma namespace #13061
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☕️ Reasoning
A bug relating to importing Prisma from a custom
output
raised in #13060 seems to be caused by previous PR #12755 where functionality was changed to import the error classPrismaClientKnownRequestError
from thePrisma
namespace.As we are only looking for code
P2025
(defined here) we do not need to import the full client.🧢 Checklist
🎫 Affected issues
Fixes: #13060 #13035
📌 Resources