PlanetScale Safe Migrations: DDL Statement Rejected

How to fix it

Try these in order — the most common fix is first.

1. 1. Use a branch and deploy request

   Copy steps
   1. Create a development branch
   2. Run your schema change there
   3. Open a deploy request and deploy it to main
   Did this fix it? Yes No

2. 2. Point ORM migrations at a branch

   Copy steps
   1. Use the branch connection string for prisma db push
   2. Then deploy via deploy request
   Did this fix it? Yes No

3. 3. Disable safe migrations (not recommended)

   Copy steps
   1. Database > Settings > Safe migrations off
   2. Risk: table locks and downtime on large tables
   Did this fix it? Yes No

Symptoms

Running ALTER TABLE or CREATE INDEX on the production branch returns a rejection error.

Why it happens

• Safe migrations enabled on the production branch (by design)
• Prisma db push or ORM migration run against production

This guide also covers

• planetscale safe migrations
• planetscale ddl rejected

Other PlanetScale errors

• PlanetScale Transaction Pool Connection Limit Exceeded
• PlanetScale Foreign Key Constraints Not Working
• PlanetScale Prisma Connection Errors
• PlanetScale Query Exceeded Row or Time Limit
• PlanetScale Postgres Import Fails or Is Slow
• PlanetScale Postgres Extension Not Available
• PlanetScale Unexpected Bill: Storage, Backups and Transfer
• PlanetScale Connection Errors During Outage