#34546: Failed migration yields to unmigratable app:""OperationalError: (1050,
"Table '<name>' already exists")
--------------------------------+--------------------------------------
Reporter: Natalia Bidart | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:2 Simon Charette]:
> I'm afraid there's little that can be done here on MySQL which doesn't
support transactional DDL.
>
> If you have a migration with multiple operations and one of them happen
to fail Django has no way to know which operations are applied and which
aren't so re-running the migration requires attempting the whole sequence
of operations again.
>
> [https://docs.djangoproject.com/en/4.2/topics/migrations/#mysql This is
a documented] limitation of MySQL.
Thanks Simon for this answer, it's both attentive and helpful!
Was it ever considered/discussed to add a message after a failed migration
pointing the user to the specific docs for further information about the
available (or not available) options (depending on the DB)?
--
Ticket URL: <https://code.djangoproject.com/ticket/34546#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187fc7d498c-efdf0d9c-29a6-4c00-8dcf-c019a083bbb3-000000%40eu-central-1.amazonses.com.
