#24236: Custom ManyToManyFields don't generate SQL database changes
-------------------------------------+-------------------------------------
Reporter: MarkusH | Owner: MarkusH
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by coldmind:
Old description:
> Regression introduced in 3d4a826174b7a411a03be39725e60c940944a7fe
>
> If a custom `ManyToManyField` doesn't define a `get_internal_type():
> return "ManyToManyField` the schema backends won't recognize it as a m2m
> field and thus don't treat it as such.
>
> This breaks existing code.
New description:
Regression introduced in 3d4a826174b7a411a03be39725e60c940944a7fe
If user writes a class, inherited from `ManyToManyField` ("custom" m2m
field) and doesn't define a `get_internal_type(): return "ManyToManyField`
the schema backends won't recognize it as a m2m field and thus don't treat
it as such.
This breaks existing code.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/24236#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.b79d80f52565cad6958cedcc0f9c24c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
