onDelete: Cascade slower with Generated PrismaClient (PlanetScale Adapter)
Hello 
- Prisma Version: 6.16.3
- Adapter: @prisma/adapter-planetscale 6.16.3
- Operation:
- Environment: Local test (Vitest) and CI/CD (GitHub Actions)
- Generated PrismaClient: ~12 seconds
Performance Issue with PlanetScale Adapter: Generated PrismaClient vs Direct @prisma/client
Problem Description
We're experiencing significant performance degradation with PlanetScale adapter when using the generated PrismaClient compared to the direct@prisma/client for cascade delete operations.Context
- Database: PlanetScale (MySQL)- Prisma Version: 6.16.3
- Adapter: @prisma/adapter-planetscale 6.16.3
- Operation:
db.user.delete() with cascade deletes- Environment: Local test (Vitest) and CI/CD (GitHub Actions)
Performance Comparison in local
- Direct @prisma/client: ~7 seconds- Generated PrismaClient: ~12 seconds