#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 Simon Charette):
> 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)?
Not that I know of. I guess we could conditionally augment the message
with a pointer at the docs when the current migration fails to apply and
isn't atomic as he same problem can also happen on backends that do
support transactional DDL for migrations that explicitly marked as `atomic
= False`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34546#comment:6>
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/01070187fcafcead-da7fc32b-4aee-4120-8c43-6acf6dba6208-000000%40eu-central-1.amazonses.com.
