Handle error `ERROR HY000 (1105): direct DDL is disabled`

PlanetScale or Vitess (with enable_direct_ddl=false) throws the following error if you try to run DDL statements on the main branch, as you are supposed to only run these in branches and deploy them via “deploy requests”:

ERROR HY000 (1105): direct DDL is disabled

To reproduce: Run any DDL statement on a main branch on a PlanetScale database.

We should catch this and output a known error message with the following message text:

Direct execution of DDL (Data Definition Language) SQL statements is disabled on this database. Please read more here how to handle this: https://pris.ly/d/migrate-no-direct-ddl

(The link currently points to a rather general issue, but will be updated to point to a specific issue or documentation later)

The Vitess instances we are testing against do not show this behavior by default, but can be configured to do so via ENABLE_DIRECT_DDL: false in docker-compose.yml.

[tomhoule]

@bigint I think this is probably because you are pushing to the main branch. Pushing to any other branch should work. We haven’t implemented special handling for this error yet.

[janpio]

That depends on how you want to use PlanetScale. You can either do that, but I am not sure if branches get the same guarantees re stability as the main branch. Or you use their branching system and merge the PR changes from the branch where you applied the migration, to your main branch (instead of using migrate deploy as you would in the normal Prisma only workflow).