We use Prisma to access a Postgres database. The query below runs very slowly. A simple modification to the SQL (also shown below) makes it orders of magnitude faster. Is there a way to tell Prisma to use the modified version. I’d like to avoid the slowdown, preferably without resorting to raw SQL.

We use Prisma to access a Postgres database. The query below runs very slowly. A simple modification to the SQL (also shown below) makes it orders of magnitude faster. Is there a way to tell Prisma to use the modified version. I’d like to avoid the slowdown, preferably without resorting to raw SQL.

I have prisma nest js project with postgresql db.

I have the createdAt and updatedAt properties in my entities inside my PostgreSQL database.

Is there a way to use Prisma ORM to do a database migration (either when adding a new column, adding a new constraint etc.) in production without data loss. I know that when you apply a new column change, that that will break SQL’s constraints since the column will be required.

I am new to Prisma. I have a Postgres data set where the entries include a field named genres that is an array of strings. I want to call to the database using prisma and return an array of distinct genres. What I want to avoid is treating an array of genres as a distinct value. Example below.

I have a Prisma model defining events stored in a PostgreSQL database. One of the fields is additionalFields, which is a JSON object. How can I construct a Prisma query to retrieve events, matching even if the additionalFields contain additional properties beyond those specified in the query? Here’s my model:

Closed 5 mins ago.

When updating or adding a value, it gives an error regarding the VariantID even though it’s defined as nullable.