#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
--------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
I'm sorry but it is support question and Trac is not a support channel.
> ValueError: The database backend does not accept 0 as a value for
AutoField.
I'm not sure how we could be clearer here. 0 doesn't work for auto
increment fields on MySQL without the `NO_AUTO_VALUE_ON_ZERO` SQL mode.
> MySQLdb.OperationalError: (1050, "Table 'testapp_modelz' already
exists")
MySQL doesn't support roll back DDL operations in a transaction.
--
Ticket URL: <https://code.djangoproject.com/ticket/34546#comment:3>
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/01070187fc6bab02-dcb732fa-8999-4d18-8926-62bbea48f9e7-000000%40eu-central-1.amazonses.com.
