#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):
Thanks Mariusz, though I wasn't looking for support, I already fixed my DB
manually.
I still felt this issue is a paper-cut for Django users and some
indication about how to proceed could be valuable for them (and that's the
reason why I created this ticket).
--
Ticket URL: <https://code.djangoproject.com/ticket/34546#comment:4>
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/01070187fc747fd2-512699b2-90f3-464b-9326-8e3885dd12e7-000000%40eu-central-1.amazonses.com.
