#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: closed
Component: Migrations | Version: 6.0
Severity: Normal | Resolution: wontfix
Keywords: AlterField, no-op, | Triage Stage: Accepted
ManyToManyField |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Clifford Gama):
* resolution: => wontfix
* status: assigned => closed
Comment:
This is likely not a feasible optimisation with the way the `db_table`
name of an auto-generated `through` model
[https://github.com/django/django/blob/6cc1231285a20b11058143f8cb0a6b4b3999b23a/django/db/models/fields/related.py#L1991-L2002
is backend aware], while the auto detector and `makemigrations` are
backend agnostic. In other words, we have nothing to compare the new
`db_table` with at `makemigrations` time if the `through` model is auto-
created.
Please reopen if I've missed something.
May be related to #33201.
--
Ticket URL: <https://code.djangoproject.com/ticket/36803#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 visit
https://groups.google.com/d/msgid/django-updates/0107019b2c02f36c-d57b1d17-c31b-4ffd-8505-492121c3f9ba-000000%40eu-central-1.amazonses.com.
