The documentation provides no indication as to why you might want to use indexes
|Reported by:||Owned by:||bbaja42|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||yes|
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*. 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.
Change History (7)
comment:1 Changed 3 years ago by
|Patch needs improvement:||unset|
|Triage Stage:||Unreviewed → Accepted|
|Type:||Uncategorized → Cleanup/optimization|