#30966: Migration crashes due to foreign key issue, depending on otherwise
irrelevant order on MySQL.
---------------------------------+------------------------------------
Reporter: Peter Thomassen | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: migration mySQL | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Changes (by felixxm):
* keywords: migration => migration mySQL
* version: 2.2 => master
* component: Database layer (models, ORM) => Migrations
* stage: Unreviewed => Accepted
Comment:
Thanks for this report, I confirmed this issue on MySQL. Scenario is
really tricky, without the last operation i.e.
{{{
migrations.AlterField(
model_name='rrset',
name='subname',
field=models.CharField(blank=False, max_length=178),
),
}}}
everything works fine. When we take it into account, migrations don't drop
a `FOREIGN KEY` constraint from `desecapi_token`.
Reproduced at 85efc14a2edac532df1a9ad4dd9b6d4a4dcf583e.
--
Ticket URL: <https://code.djangoproject.com/ticket/30966#comment:2>
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/072.67a0d436e7cc6493ad23b55f8fb752e5%40djangoproject.com.
