Alberto Schiabel

Hi, can you please give me more details? Are you on Android or iOS? Which version? Are you using a physical device or an emulated one? Do you have any...

Hi @hanar3, if I understood correctly, you currently: - generate `prisma` types of a project in a system (e.g. windows) - (I assume) commit those `prisma` output files and push...

Hi @FredLackeyOfficial, would you please be able to share a minimal project that allows us to reproduce the issue you're describing? Knowing how to exactly trigger this bug would allow...

Hi @johncblandii, could you please share the rest of the `prisma.schema` model? For instance, the definitions of `League` and `Team` could prove useful for us to understand this issue.

Thank you @tomhoule. While the misleading error part of the issue still stands, I appreciate that your suggestion indeed allows to query. Beforehand, I had also tried with SELECT *...

I believe this is the root issue: https://github.com/grpc/grpc-node/issues/1405

Hi @stultuss, is there any chance you've found a viable solution / workaround?

Thank you for opening this issue. Closing this in favour of https://github.com/prisma/prisma/issues/8832, which we were recently able to reproduce (different Prisma Client query, but same problem under the hood). We're...

We have closed the original issue in `[email protected]`, please see [this comment](https://github.com/prisma/prisma/issues/8832#issuecomment-1260533913).

Considering that we only support `InnoDB`, I confirm that `SET DEFAULT` only works from `mysql:8`, as shown [here](https://github.com/prisma/prisma/issues/14673#issuecomment-1269790213).