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.
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...