#32674: DEFAULT_AUTO_FIELD changes should be detected for PKs of auto-created
intermediate M2M models.
-------------------------------------+-------------------------------------
Reporter: Cristiano Coelho | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 4.0
Severity: Normal | Resolution:
Keywords: DEFAULT_AUTO_FIELD | Triage Stage: Accepted
AutoField BigAutoField |
ManyToManyField |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: Simon Charette, Andrew Godwin, Shai Berger, Markus Holtermann
(added)
* version: 3.2 => 4.0
* type: Bug => New feature
* severity: Release blocker => Normal
Comment:
I tried, I really really tried, but after few days of using different
approaches I need to conclude that this is massive, extremely complicate,
and maybe even unfeasible. As far as I'm aware we've never took into
account changes in auto-created many-to-many tables except for those
directly related with a definition of `ManyToManyFields`. A project state
used by migrations autodetector doesn't include auto-created model, so the
only fix that I can imagine would require including `through_pk_type` in
the `ManyToManyField.deconstruct()` but it's also tricky and error-prone.
We're going to document this caveat and treat this ticket as a new
feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/32674#comment:2>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/070.93a02e47c274082c696bb52b2116b28e%40djangoproject.com.
