#24236: Custom ManyToManyFields don't generate SQL database changes
-------------------------------------+-------------------------------------
Reporter: MarkusH | Owner: MarkusH
Type: Bug | Status: closed
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Markus Holtermann <info@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"f8c040e1676506e3bcba5f2744199fdcde430552"]:
{{{
#!CommitTicketReference repository=""
revision="f8c040e1676506e3bcba5f2744199fdcde430552"
[1.7.x] Fixed #24236 -- Treated inherited m2m fields as such if they don't
define get_internal_type()
Regression introduced in 3d4a826174b7a411a03be39725e60c940944a7fe
Thanks IRC user ris for the report, Loïc Bistuer, Anssi Kääriäinen and
Andriy Sokolovskiy for the discussion and Tim Graham for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24236#comment:11>
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.fb5270d5c74c7f3d9e739b7ae5f70dc1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
