#36800: Issue with ManyToManyField renaming
-------------------------------------+-------------------------------------
Reporter: Josik | Owner: Clifford
| Gama
Type: Bug | Status: assigned
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* cc: Simon Charette (removed)
Comment:
Not sure why I was pinged here and on Discord if there was already a
patch, it gave me the impression there was an urgent need for me to look
at this.
The proposed solution looks right to me albeit we might want to adjust the
comment about no field alteration needed to take place if the name change
as that's no true for many-to-many fields and likely what made us miss
this in the first place.
Here's [https://github.com/django/django/pull/20412/ where I got during my
plane trip].
--
Ticket URL: <https://code.djangoproject.com/ticket/36800#comment:7>
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/0107019b240b2f2d-3ed1a384-4b92-4075-83c5-6df038a84574-000000%40eu-central-1.amazonses.com.
