@pfigel @angristan To hazard a guess, the terminal output there looks like it was a resumed migration that failed between adding the new foreign constraints to the column and dropping the old one. That's not a place the migration says it's safe to kill it (because it's not), but we could probably handle that a bit better (by removing the constraints ourselves).

@angristan @pfigel (To be clear, it looks like you're in a safe state, just that it died in a pretty difficult to recover from section. Removing the foreign keys and re-running it as you did should fix that specific problem, though.)

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!