#32675: Migration autodetector detects unnecessary changes.
--------------------------------------------+------------------------
Reporter: Mariusz Felisiak | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 4.0
Severity: Release blocker | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------------+------------------------
Migration autodetector detects nonexistent changes in `ForeignKey`, it's
probably because previous migrations have the `to_field` parameter. For
Django itself it detects two changes:
- `django/contrib/admin/migrations/0004_alter_logentry_content_type.py`
{{{
migrations.AlterField(
model_name='logentry',
name='content_type',
field=models.ForeignKey(blank=True, null=True,
on_delete=django.db.models.deletion.SET_NULL,
to='contenttypes.contenttype', verbose_name='content type')
),
}}}
- `django/contrib/auth/migrations/0013_alter_permission_content_type.py`
{{{
migrations.AlterField(
model_name='permission',
name='content_type',
field=models.ForeignKey(on_delete=django.db.models.deletion.CASCADE,
to='contenttypes.contenttype', verbose_name='content type'),
)
}}}
Regression in aa4acc164d1247c0de515c959f7b09648b57dc42 (see #29899).
--
Ticket URL: <https://code.djangoproject.com/ticket/32675>
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/050.9d4e857c7cc786790ccf737963aa9316%40djangoproject.com.
