You can take the multiple migrations approach and for a short time keep two status fields while you change over, eventually dropping the first and renaming the

You can take the multiple migrations approach and for a short time keep two status fields while you change over, eventually dropping the first and renaming the second. Or, as most people would do it, within a transaction add the new value to your enum and run an update. Of course, this can't be reversed but if it's a simple `set status = 3 where status = 4` I don't see the problem.