AJ Holloway
AJ Holloway
Bump on this
Another bump on this issue. Currently doing raw multiple inserts with on conflict do update set
``` export const DBConn = new PrismaClient({ log: [ { emit: 'stdout', level: 'error', }, { emit: 'stdout', level: 'info', }, { emit: 'stdout', level: 'warn', }, ], }) .$extends({...
@morintd here's an example of how I use it
Would LOVE to see this merged in as I've recently run into this issue while running Prisma in Kubernetes in GCP.
+1 on this. Currently I've changed my update to only return one field but that's just a workaround. Often the select is the more costly than the create/update itself.