Support for manually managing prepared statements about prisma HOT 5 OPEN

Prisma actually uses prepared statements under the hood and also caches and reuses them.

I hence renamed the issue a tiny bit to make this a request for "manually managing" prepared statements.

from prisma.

Prisma actually uses prepared statements under the hood and also caches and reuses them.

I hence renamed the issue a tiny bit to make this a request for "manually managing" prepared statements.

If so, suppose if I have a conditional parameter like this

const isUsername = true
const username = "kavya"

PrismaClient.users.findUnique(
  isUsername ? { where: { username } } : { where: { email: username } }
);
// there can be two different prepared sql query which are 
// 1) select x,y,z from users where username="kavya"
// 2) select x,y,z from users where email="kavya"

Is this handled by prisma caching mechanism? like which query to select form cache.
It gets even more complicated when using multiple conditional statement in complex queries.

from prisma.

Yes, when executing these different "paths" different queries are generated - and the correct prepared statement from the cache is used for each case.

from prisma.

Alright, that's nice but still we need a manual prepared statement feature to optimize queries further and remove redundant overhead. Are contributors actively working on this?

from prisma.

We at Prisma are not.

from prisma.