This page describes features that are currently not supported by Prisma and are not planned to be supported.
Records must be uniquely identifiable
Prisma currently only supports models that have at least one unique field or combination of fields. In practice, this means that every Prisma model must have either at least one of the following attributes:
@@idfor a single- or multi-field primary key constraint (max one per model)
@@uniquefor a single- or multi-field unique constraint
Manual database connection handling
When using Prisma, the database connections are handled on an engine-level. This means they're not exposed to the developer and it's not possible to manually access them.
Prisma Migrate limitations
Was this helpful?
Edit this page on GitHub