Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documenting rule-of-thumb when optimizing DB usage with indexes... #2360

Closed
wants to merge 1 commit into from

Conversation

alextreme
Copy link
Contributor

with a number of caveats to hopefully deter readers from using indexes everywhere. For ticket #21989

Based on #2252 from bbaja42

@colons
Copy link
Contributor

colons commented Feb 23, 2014

Awesome.

@alextreme
Copy link
Contributor Author

Thanks! Apologies for not conforming to the Django committing guidelines regarding my commit message, I will do so for future commits.

@charettes
Copy link
Member

@alextreme it's not too late to change your commit message. You can simply use git commit --amend and force push your changes to your ticket-21986 branch.

@sergeykolosov
Copy link
Contributor

Probably, it is also worth mentioning usages of Model.Meta.ordering, ModelAdmin.date_hierarchy, ModelAdmin.list_filter and ModelAdmin.ordering.

@timgraham
Copy link
Member

merged in c8d61fa, thanks.

@timgraham timgraham closed this Mar 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants