Flavian Desverne comments

Results 104 comments of


                                            Flavian Desverne

`{ not: true }` doesn't return `null` results

Hey folks, we're closing this issue in favor of https://github.com/prisma/prisma/issues/24252

Bring back `t.prismaType` on the v2

Nexus plugins needs to be released for this to work. Currently blocked by: https://github.com/prisma-labs/nexus/pull/236

Type Mismatch Error When Using `connect` and `connectOrCreate` in Prisma Model Relation

Hey @codeicetea, your reproduction is unfortunately incomplete. We're missing the `Employees` relation for us to set the `trainerId`. We're also missing what your data payload initially contains. Could you please...

feat(schema-engine): add support for multiple split schema files

Had to create a new PR because of stacked PRs and conflicts I could handle. I'm closing this one in favor of https://github.com/prisma/prisma-engines/pull/4874

`Entered unreachable code` using an illegal connection string

Hey @MagnusOestlund, Thanks for the thorough reproduction steps. This will be very useful for us 🙏

2x worse performance when running raw queries in Prisma vs `pg`

Hey folks, we're about to release Prisma 5.17.0 and it comes with performance improvements on queryRaw. On our side, we've measured up to 2x perf improvements compared to Prisma 5.16.0,...

Could not figure out an ID in create

Hey @Sonichigo , Would you mind sharing any additional information so that we can reproduce your issue? Your datamodel and some Prisma Client query that reproduces this bug is capital...

Could not figure out an ID in create

Hey @Sonichigo, Would you mind trying with a newer version of Prisma and confirm whether the bug is still present? Thank you 🙏

Expected parent IDs to be set when ordering by parent ID.

Hey @DarkWorldCoder , Do you have any idea, in the snippet you have shared, which query specifically reproduces the error you're seeing? The bug you've encountered is likely specific to...

PANIC: timer has gone away

Hey @shafayetullah7 , Would you mind sharing any additional information so that we can reproduce your issue? Your datamodel and some Prisma Client query that reproduces this bug is capital...