Models that can be ignored by migration scripts (Support for views)

[kings1ay3r]

Problem

The lack of support for database views have already been discussed for quite long, and various work arounds have also been suggested in those discussions. The project I work on extensively uses views to roll-up data & the task of managing them, everytime there is a migration is frustrating and error prone.

Suggested solution

Add support for viewModel or an annotation like @view or @ignore in the schema file so that the migrate script can create a view instead of a table/relationship using the corresponding syntax for the target DBMS where supported or throw an error if views arent supported. Client generation can generate only read methods / keep the other methods unexported. view defenitions can take references and aggregate methods.

Alternatives

View defenitions can be done by manually editing the migration sql.

[Jolg42]

Note: relevant issue about supporting database views #678

[TasinIshmam]

Hi folks, Tasin from the Prisma team here 👋

We know you are waiting for database views to land in Prisma.

As you might have seen, this is currently a candidate feature on our roadmap for the Prisma ORM. At this point in time, we can't really give an estimate of when this feature will be available on the ORM.

That being said: Another team at Prisma is working on solving this problem in different ways (beyond the Prisma ORM) — especially for users of sererless environments.

To figure out what exactly you, our users, are looking for, we launched a Design Partner Program where we collaborate closely with external teams to dive deep into their problems.

If you’re struggling with database views, especially in a serverless environment, you might be a great fit for this program!

You can check out the program in more detail to see the kinds of activities we’re planning. To apply to this program, fill out the application form.

We’re looking forward to hearing from you!

[janpio]

This is now obsolete as we implemented a new view keyword behind that views preview feature, which is ignored in Migrations. Read more via the links in our preview feature feedback issue for Views: #17335