#37049: Changing a m2m through= from one custom model to another is no-op'd
instead
of raising an error
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Clifford
| Gama
Type: Bug | Status: assigned
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: migrations, | Triage Stage: Accepted
ManyToManyField, through |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* stage: Unreviewed => Accepted
Comment:
Thank you Clifford! Well spotted!
--
Ticket URL: <https://code.djangoproject.com/ticket/37049#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 visit
https://groups.google.com/d/msgid/django-updates/0107019dac1d626a-ee66fe0a-48d4-4f01-bfb6-db4a00a75727-000000%40eu-central-1.amazonses.com.
