Most SQL databases support views and materialized views.
It should be possible to have a type in a Prisma service that is backed by a view or materialized view. These types would not generate mutations.
The underlying view or materialized view can either be managed by Prisma or already exist in the database.
Hey @sorenbs is there an update for this?
As far as api goes, any thoughts on a schema directive @pgView with 2 params: view name & optional select statement? Come migrations, generate the create or replace view statement. @pgMaterializedView directive could add an argument for a cron frequency.
Any Updates ?