#36803: Make AlterField a no-op when ManyToManyField's through.db_table remains
the
same between renames.
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Clifford
Type: | Gama
Cleanup/optimization | Status: new
Component: Migrations | Version: 6.0
Severity: Normal | Resolution:
Keywords: AlterField, no-op, | Triage Stage: Accepted
ManyToManyField |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Clifford Gama):
* has_patch: 0 => 1
* resolution: wontfix =>
* status: closed => new
Comment:
We can still optimise when there is an explicit `db_table`. I opened a
[https://github.com/django/django/pull/20444 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/36803#comment:5>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019b4749a5b2-ff937033-b1df-48e9-988c-422c959b89c3-000000%40eu-central-1.amazonses.com.
