Jan Piotrowski

Yes, Client middleware or Client extension (or handle on the database side somehow without Prisma involvement).

Prisma does not support this functionality right now. A string is a string, and an enum is an enum. You could probably prevent adding unwanted values via a simple middleware,...

(Might be worth creating a separate, explicit feature request issue for the idea "ability to override the types generated by the schema and give developers more flexibility on controlling the...

Related: https://github.com/prisma/prisma/issues/13451 + https://github.com/prisma/prisma/issues/7158

@jonschlinkert That happens via the underlying SQL query that is used to create a view `UserInfo` that has three fields `id`, `name` and `type`? See this documentation section for an...

Would you have been able to easily identify any of the columns as `@unique` in your view? It will be quite some while until we can fully get rid of...

You would also be able to use `@@unique([first_id, second_id])` as a compound unique if you include both fields in the view. (Sorry, missed to mention that above - we would...

@Ustice @jonschlinkert If you are using PostgreSQL, have a look at this comment I just posted at the feature request issue: https://github.com/prisma/prisma/issues/678#issuecomment-1412344738

We do not communicate concrete timelines - that never ends well. It is probably more towards the bottom of our feature list for views, because: You can already create a...

Yes, something in that direction is also our current thoughts re how to support creation and migration of views @luke-cbs. We can not "generate" the SQL from the `view` definition...