New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PANIC in libs/prisma-models/src/record.rs:161:30 | Invalid coercion encountered: ConversionFailure("Bytes #7097
Comments
So I'm using BlitzJs as well and I recall I'm using the same table. It's using version 2.20.1. I rolled back NestJS to use the same version. No problems at all. Just fyi. 😺 |
Thanks, that instantly increases the priority here as it is a regression. We will look into this asap. |
I can reproduce this, thanks for the detailed reproduction. |
I just filed a very similar bug to this, #7214. I have experienced this on all versions after 2.21.2 |
Any updates on this? |
I just ran into this as well - it's a bit of a blocker for me using Prisma at the moment. I did a little testing and found that this works: model Example {
id BigInt @id @default(autoincrement())
uuid Bytes @db.Binary(16)
createdAt DateTime @default(now()) @map("created_at") @db.Timestamp(6)
title String
} However this does not: model Example {
id BigInt
uuid Bytes @id @db.Binary(16)
createdAt DateTime @default(now()) @map("created_at") @db.Timestamp(6)
title String
} Which leads me to believe it has something to do with the |
Any updates? I'm frozen on 2.20. Right now it's fine, until something massive this way comes. |
I was in Slack chatting with Ryan over an issue I have. He's unable to debug, due to this issue persisting. Any updates? Thanks https://prisma.slack.com/archives/CA491RJH0/p1626944945334900 |
This comment has been minimized.
This comment has been minimized.
@pantharshit00 Thank you so much for the update. You are right, in hindsight it's off-topic so I have deleted it. |
This will be fixed in 2.29. |
Bug description
I'm getting an issue where with NestJS, doing a findFirst where a table has multiple binary columns results in a panic.
Can't post the full https links as it's too big for github. Hopefully the following will do instead.
How to reproduce
simple query on data should suffice.
Expected behavior
Should not crash and show result.
Prisma information
Using NestJS:
Models:
Data:
Environment & setup
Have tried past 2 versions and same result.
The text was updated successfully, but these errors were encountered: