Pain point · Self-hosting & upgrades · Causes churn
Fresh install fails at prisma migration with missing BIN_TO_UUID function
6 source threads · first seen 2022-08 · last seen 2025-05
Summary
On a fresh MySQL deployment, the 05_add_visit_id migration fails, blocking all further migrations and startup.
- Affects
- self-hoster on MySQL
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“I tried to go back to V2.17 and I have the same problem”
“A migration failed to apply. New migrations cannot be applied before the error is recovered from”
“I updated the docker image to the latest version and got a `prisma migrate deploy` command error after container boot”
“The column `account.account_uuid` does not exist in the current database after upgrading to 1.39.2”
“The update to 1.37.0 did not work out however:”
“The migration `01_init` is already recorded as applied in the database”