#10414: select_related ignores unrecognized fields
-------------------------------------+-------------------------------------
Reporter: trebor74hr | Owner:
Type: Bug | trebor74hr
Component: Database layer | Status: assigned
(models, ORM) | Version:
Severity: Normal | Resolution:
Keywords: select_related | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by anonymous):
Can anyone explain in plain simple words why fixing this issue could cause
some sort of performance problems? When you call select_related() without
any parameters django knows the structure of tables to be joined. Is it
that big performance problem to parse the string
'table__nexttable__blabla' and check it against this structure?
This issue can be annoying, when you use select_related to avoid
bombarding the DB with additional selects, and you make a small typo then
your code WILL actually bombard the db with these unnecessary selects and
you won't even know about it.
--
Ticket URL: <https://code.djangoproject.com/ticket/10414#comment:18>
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/068.22bf56a16b674586f860da76d38061a7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
