Matt Mueller

Thanks for the suggestion @yuval-hazaz! I like your suggestion of offering some options in the transaction API that could do this. That could also be a good place for transaction...

@yuval-hazaz did you also try the following? ```ts const [ignore, userList, updateUser] = await prisma.$transaction([ prisma.$executeRaw(`SET current_user_id = ${currentUser.id}`), prisma.post.findMany({ where: { title: { contains: 'prisma' } } }), prisma.post.count(),...

@thecodeah, @darioielardi, and @flybayer expressed concerns with this proposal. Each query you write needs to explicitly exclude private fields. They would prefer an "exclude-by-default" approach. To complicate matters, being able...

Thanks @scriptcoded, that's indeed a mistake in the code on my part, the proposal should be: ```js const prisma = new PrismaClient({ exclude: { user: { password: true } }...

Hey all, sorry for the lack of updates on this one. The TL;DR is we're still working on it. To clarify the possible solutions: **1. Exclude per query** ```ts prisma.user.findMany({...

Hey @bb-art, does this document answer your question? https://www.prisma.io/docs/concepts/components/prisma-client/group-by

Related issue: https://github.com/prisma/prisma/issues/13880, though more about how the Prisma Client coerces nulls in to empty lists. Likely solved together.

We just wrote some documentation on how to add custom validation with Prisma: https://www.prisma.io/docs/concepts/components/prisma-client/custom-validation We do plan to implement this feature into the Prisma Client eventually, but this is meant...

That's a good point @KhushrajRathod. It's a new ecosystem with lots of opportunity to grow. Supporting Deno is definitely on our list and something we'd like to start looking into...

Very cool. Just did a quick check, definitely some work, but here's what I would probably do. #### 1. Create a sample Prisma project 1. `npx prisma init` 2. Write...