P
Prisma•2mo ago
Scott

Prisma push to PlanetScale development branches crashing schema engine

Running prisma db push to a PlanetScale development branch is crashing the schema engine: (Vitess) 
Environment variables loaded from prisma/.env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": MySQL database "[REDACTED]" at "aws.connect.psdb.cloud"
Oops, an unexpected error occurred!
Error in Schema engine.
Reason: [schema-engine/sql-schema-describer/src/mysql.rs:307:21] called `Result::unwrap()` on an `Err` value: "Getting table_name from Resultrow ResultRow { columns: [\"f0\", \"f1\", \"f2\"], types: [Unknown, Unknown, Unknown], values: [Value { typed: Bytes(Some([99, 97, 108, 108, 95, 101, 120, 112, 111, 114, 116, 115])), native_column_type: None }, Value { typed: Text(Some(\"\")), native_column_type: None }, Value { typed: Text(Some(\"\")), native_column_type: None }] } as String failed"             
Environment variables loaded from prisma/.env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": MySQL database "[REDACTED]" at "aws.connect.psdb.cloud"
Oops, an unexpected error occurred!
Error in Schema engine.
Reason: [schema-engine/sql-schema-describer/src/mysql.rs:307:21] called `Result::unwrap()` on an `Err` value: "Getting table_name from Resultrow ResultRow { columns: [\"f0\", \"f1\", \"f2\"], types: [Unknown, Unknown, Unknown], values: [Value { typed: Bytes(Some([99, 97, 108, 108, 95, 101, 120, 112, 111, 114, 116, 115])), native_column_type: None }, Value { typed: Text(Some(\"\")), native_column_type: None }, Value { typed: Text(Some(\"\")), native_column_type: None }] } as String failed"
I've noticed a couple other people seem to be running into this today: https://github.com/prisma/prisma/issues/27734 Is this a known thing? Is there a workaround or is this a new issue? This is blocking development work. This was a routine change of adding a new table to a large project that has been using Prisma for many years. Currently on Prisma 6.8.2, but the issue is also present above on a newer version (6.10.1) per the issue.
GitHub
prisma db push panics on PlanetScale: **called Result::unwrap() o...
Bug description Running yarn prisma db push against a PlanetScale (Vitess) development branch crashes the schema engine with: Origin of the problem The very first command I ran was yarn prisma migr...
6 Replies
Prisma AI Help
Prisma AI Help•2mo ago
You selected to wait for the human sages. They'll share their wisdom soon. Grab some tea while you wait, or check out #ask-ai if you'd like a quick chat with the bot anyway!
oneonetwothree
oneonetwothree•2mo ago
This is also happening to my team (new today). We've have been using Prisma + PlanetScale for >18 months This is severely impacting our production environment Would appreciate any assistance ASAP! Thanks!
Scott
ScottOP•2mo ago
Since this spans many versions of Prisma, I am going to hedge a guess and say that something changed on the PlanetScale side. I've sent an email via PlanetScale support to see if they are aware / can provide a changelog to try and figure out what is going on. However, our PlanetScale spend is quite low, so if anyone else has a bit more support power please do the same 🙏
Scott
ScottOP•2mo ago
No description
Scott
ScottOP•2mo ago
Update from PlanetScale support. It seems like Prisma is not playing ball with Vitess 22 Ok update: It is Vitess 22. They downgraded me to Vitess 21, and now it is working again. Obviously there is still an underlying issue here between Vitess 22/PlanetScale <> Prisma, but if you are in urgent need of a fix, open a ticket with PlanetScale support. They were really fantastic.
Nurul
Nurul•2mo ago
Hey Scott! As you said, we were in touch with PlanetScale team and the issue was indeed related to Vitess upgrade. I see the fix was merged recently: https://github.com/vitessio/vitess/pull/18489 Hopefully this should be resolved very soon.
GitHub
Fix for simple projection showing no fields by dbussink · Pull Req...
When a simple projection ends up in a statement that is prepared, we end up directly calling buildFields from GetFields. When we do that, we don&amp;#39;t do the same check we do on results, which ...

Did you find this page helpful?