#21986: The documentation provides no indication as to why you might want to use
indexes
---------------------------------+--------------------
Reporter: django-issues@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
---------------------------------+--------------------
Indexing is not an inherently straightforward and intuitive concept.
There's plenty of material out there that suggests where you might want to
apply database indexes, but the Django documentation doesn't suggest
*anything*. [https://docs.djangoproject.com/en/dev/topics/db/optimization/
Database access optimization] suggests that it is a number one priority,
and that you should use the information you have gleaned from profiling to
decide what to index, but provides no methodology for applying that
information. It's left to the reader's imagination to decide if they
should add indexes to fields they read a lot or fields they change a lot
or fields they do lookups by a lot or fields that have fish puns in their
names.
I'd make some suggestions, but I am not qualified enough to write anything
I'd be at all confident in.
--
Ticket URL: <https://code.djangoproject.com/ticket/21986>
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/066.4e9c41bc78f33ef2aa390716aaad0ff9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
