fix: correct PrismaClient import path #6929
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nikolasburk
reviewed
Jun 11, 2025
...00-start-from-scratch/110-relational-databases/250-querying-the-database-node-postgresql.mdx
Outdated
Show resolved
Hide resolved
…atch/110-relational-databases/250-querying-the-database-node-postgresql.mdx
nikolasburk
approved these changes
Jun 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes an incorrect path for
PrismaClientin "Querying the database using JavaScript and PostgreSQL" page, in "Write your first query with Prisma Client" section.The documentation currently uses:
But the correct import path (for this context) is:
The recommended import path for certain setups has been updated, and this section/page has outdated syntax, which could lead to confusion or errors for users following the docs.