#36803: Make AlterField a no-op when ManyToManyField's through.db_table remains
the
same between renames.
-------------------------------------+-------------------------------------
Reporter: Clifford | Owner: Clifford Gama
Gama |
Type: | Status: assigned
Cleanup/optimization |
Component: Database | Version: 6.0
layer (models, ORM) | Keywords: AlterField, no-op,
Severity: Normal | ManyToManyField
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
[https://github.com/django/django/pull/20412#issue-3732276360 As suggested
by Simon]. Similar to f05cc5e3d2ae7663dbd248029bcb74500cf1029f (for
`db_table` on foreign keys) and #31825 for `db_column`s.
--
Ticket URL: <https://code.djangoproject.com/ticket/36803>
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/0107019b261c0a27-e544e89e-02ec-41ef-bcd2-116ac004dca0-000000%40eu-central-1.amazonses.com.
