#23435: GFK should be indexed
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by alexanderad):
Oh, so, this means that {{{Person}}} in fact has no abstract model columns
in its table. In this case that makes sense.
One more thing: it seems that {{{cls._meta.local_fields}}} is not
guaranteed to be fully populated during {{{contribute_to_class}}} call, is
it? From run to run I'm getting different set of fields in
{{{local_fields}}} during {{{contribute_to_class}}} calls.
However, the order of calls are always consistent, for example,
{{{Person}}} gets contributions from itself
({{{Person.content_object_concrete}}}), then from {{{BasePerson}}} and
finally from {{{AbstractPerson}}}.
I need to go deeper.
--
Ticket URL: <https://code.djangoproject.com/ticket/23435#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.b76576175a734455d4c4ea3bbd8816f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
