#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: assigned
Component: Migrations | Version: 6.0
Severity: Normal | Resolution:
Keywords: AlterField, no-op, | Triage Stage:
ManyToManyField | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* component: Database layer (models, ORM) => Migrations
Comment:
Thanks. #33197 is another similar fixed ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/36803#comment:1>
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/0107019b278c932b-541f1ac3-8112-49d8-b3cc-48c8ada21993-000000%40eu-central-1.amazonses.com.
