Return the relationship to VIEW
### Bug description please return the relations to View or give the ability to enable them. This is how I connected two schemas in one database. The second schema was used in the admin application. Now my .prisma file has errors everywhere: The field `bonus` is part of a relation that references a view. Relations currently cannot be used with views.Prisma. It's all because of Prisma Visual Studio Code Extension ### Severity 🚨 Critical: Data loss, app crash, security issue ### Reproduction <!-- Link to CodeSandbox, GitHub repo, or step-by-step instructions --> ### Expected vs. Actual Behavior I want to be able to connect view and model via relationships again ### Frequency Consistently reproducible ### Does this occur in development or production? Both development and production ### Is this a regression? <!-- e.g., "Yes, last worked in Prisma 5.1.0, broke in 5.2.0" --> ### Workaround <!-- e.g., "Downgrading to Prisma 5.1.0 fixes it" or "No workaround found" --> ### Prisma Schema & Queries ```prisma // Add relevant schema.prisma snippet ``` ```ts // Add relevant Prisma Client query ``` ### Prisma Config ```ts // Add your `prisma.config.ts` ``` ### Logs & Debug Info ``` // Debug logs here ``` ### Environment & Setup - **OS:** <!-- macOS, Windows, Debian, CentOS, etc. --> - **Database:** <!-- PostgreSQL, MySQL, PlanetScale, etc. --> - **Node.js version:** <!-- Run `node -v` --> ### Prisma Version ``` // Prisma version output ```
Posted by SonderRill on Jul 29, 2025, 3:51 PM
Tags
Related issues
- Many devs love to shit on the guy from the 'I just want the exe.
- Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
- Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
- I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
- Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
- I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
reliability (SaaS)
Many devs love to shit on the guy from the 'I just want the exe.
Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
App broken with Mosquitto broker 7.0.0
[BUG] Remote Control: automatic reconnection doesn't work -- connection drops silently with no recovery
Return the relationship to VIEW
### Bug description please return the relations to View or give the ability to enable them. This is how I connected two schemas in one database. The second schema was used in the admin application. Now my .prisma file has errors everywhere: The field `bonus` is part of a relation that references a view. Relations currently cannot be used with views.Prisma. It's all because of Prisma Visual Studio Code Extension ### Severity 🚨 Critical: Data loss, app crash, security issue ### Reproduction <!-- Link to CodeSandbox, GitHub repo, or step-by-step instructions --> ### Expected vs. Actual Behavior I want to be able to connect view and model via relationships again ### Frequency Consistently reproducible ### Does this occur in development or production? Both development and production ### Is this a regression? <!-- e.g., "Yes, last worked in Prisma 5.1.0, broke in 5.2.0" --> ### Workaround <!-- e.g., "Downgrading to Prisma 5.1.0 fixes it" or "No workaround found" --> ### Prisma Schema & Queries ```prisma // Add relevant schema.prisma snippet ``` ```ts // Add relevant Prisma Client query ``` ### Prisma Config ```ts // Add your `prisma.config.ts` ``` ### Logs & Debug Info ``` // Debug logs here ``` ### Environment & Setup - **OS:** <!-- macOS, Windows, Debian, CentOS, etc. --> - **Database:** <!-- PostgreSQL, MySQL, PlanetScale, etc. --> - **Node.js version:** <!-- Run `node -v` --> ### Prisma Version ``` // Prisma version output ```
Comments (0)
No comments yet. Start the discussion.