#13730 closed (fixed)
Allow db_index=False for ForeignKey
Reported by: | Alexander Schepanovski | Owned by: | Alexander Schepanovski |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 1.2 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Now db_index=True is hard-coded, so I have to drop unneeded indexes manually after syncdb or south migrate.
Rationalization:
Indexes slow down insert, update and delete operations, so it's ineffective to manage indexes that are not really used.
They may be not used if:
- they are created for consistency not for joins;
- there are partial, multiple column or other special indexes that would be used instead of them
Attachments (2)
Change History (8)
by , 14 years ago
Attachment: | needs_context.diff added |
---|
by , 14 years ago
Attachment: | soft_db_index.diff added |
---|
comment:1 by , 14 years ago
Has patch: | set |
---|
comment:2 by , 14 years ago
Owner: | changed from | to
---|
comment:3 by , 14 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:4 by , 14 years ago
Status: | new → assigned |
---|---|
Triage Stage: | Accepted → Ready for checkin |
Promoting to ready for chekin since it's obvious bug
comment:5 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:6 by , 14 years ago
Note:
See TracTickets
for help on using tickets.
Sorry, first patch is for other issue.