Replies: 2 comments
-
|
Hi @cghiurea! Your understanding is correct! I understand how this could look repetitive, I have already shared this feedback with our ORM team to get insights on how we could prevent duplication. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, As we have not heard back from you, we are closing this discussion to keep our discussions organized. Feel free to start a new discussion if this remains relevant. Thank you for being part of the community! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Question
In Prisma 7, I'm required to configure the database URL in two places:
In prisma.config.ts for the CLI:
And again when instantiating the client with an adapter:
This seems redundant. In Prisma 6, I only specified the URL in the schema and didn't need to pass it again when creating the client.
Questions:
Is one settings for the client and the other for the dev prisma?
Is there a way to avoid duplicating the URL configuration? Before both the client and prisma used the prisma.schema for the database url
How to reproduce (optional)
No response
Expected behavior (optional)
No response
Information about Prisma Schema, Client Queries and Environment (optional)
prisma : 7.0.1
@prisma/client : 7.0.1
Operating System : darwin
Architecture : arm64
Node.js : v24.8.0
TypeScript : 5.9.3
Query Compiler : enabled
PSL : @prisma/prisma-schema-wasm 7.1.0-2.f09f2815f091dbba658cdcd2264306d88bb5bda6
Schema Engine : schema-engine-cli f09f2815f091dbba658cdcd2264306d88bb5bda6 (at node_modules/.pnpm/@prisma[email protected]/node_modules/@prisma/engines/schema-engine-darwin-arm64)
Default Engines Hash : f09f2815f091dbba658cdcd2264306d88bb5bda6
Studio : 0.8.2
Beta Was this translation helpful? Give feedback.
All reactions