#25461: Mistake in model _meta API migration guide for multi-table inheritance
-------------------------------+------------------------------------
Reporter: ad-65 | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 1.8
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"ca7b926c8558f6e9bbd33a748bc53235b909e29a" ca7b926]:
{{{
#!CommitTicketReference repository=""
revision="ca7b926c8558f6e9bbd33a748bc53235b909e29a"
[1.9.x] Fixed #25461 -- Corrected meta API code examples to account for
MTI.
In the case of multiple-table inheritance models,
get_all_related_objects() and
get_all_related_objects_with_model() don't return the auto-created
OneToOneField, but the new examples didn't account for this.
Backport of 8be84e2ac42b2556fd6fa07794b3708b143ef341 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25461#comment:10>
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/063.76bafa18c957befd147c03d575881ad3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
