#37034: Improve writing migrations how-to add through field on a ManyToManyField
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Clifford
| Gama
Type: Bug | Status: assigned
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: migrations, | Triage Stage:
ManyToManyField, through | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* cc: Adam Johnson (added)
Comment:
So from my understanding, this section of the docs was added to add an
example of using `SeperateDatabaseAndState` rather than showing the best
way to change a `ManyToManyField` to use a `through` model. See
https://github.com/django/django/pull/12523 for details.
So I suppose my question would be, do you have a better example for using
`SeperateDatabaseAndState`?
--
Ticket URL: <https://code.djangoproject.com/ticket/37034#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/0107019d8ba30e9d-ee6e2cf9-b060-4756-b73e-c008f1cfde6f-000000%40eu-central-1.amazonses.com.
