Serhii Tatarintsev

The question is not about `in` operator though, it's about `every`, which does not exist in pure SQL (`ALL` operator, despite similar sounding name, works very differently and can't be...

@apecollector `every` means that condition individually applies to every item in a relationship. What you query does is basically, "Give me all posts, where every tag is both `{ name:...

> Given Prisma 6.1 is due to be released later today, could we get some attention here to loosen the restrictions @SevInf ? Hey @erawk, I no longer work for...

Hey @jazzybruno. Would [result extensions](https://www.prisma.io/docs/orm/prisma-client/client-extensions/result) solve your usecases?

Before we even start to talk about timelines, we have to agree on whether or not this is feature worth having. How would the field be accessible on the model?...

>yes, that's indeed not desireable. Would you have any advice to bypass the string serialisation of i64? Is [this idea](https://github.com/prisma/team-orm/issues/1065#issuecomment-2024954101) still valid?

Copying what I wrote in Slack in conversation with @jkomyno: What I am thinking the best course of action here: do this change in D1 adapter code, not in the...

Hi @Typeve! We've identified and fixed the issue. Could you try dev snapshot version `5.18.0-integration-fix-config-dir-client.5` and see if the problem still happens for you? We don't recommend using dev snapshot...

@Typeve thank you for confirmation! Yes, most likely 5.18.0 will be the first stable version to receive the fix. In the meantime, you can workaround the issue by explicitly providing...

Hi @david-ember. I can not reproduce the issue. `SELECT 1` query returns `[ { '?column?': 1 } ]` for me. Could you provide a reproduction repository that we can run...