#7186 closed (fixed)
Django creates redundant unique index for OneToOneField on MySQL
Reported by: | Peter Melvyn | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Keywords: | qsrf-cleanup MySQL redundant unique index | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I've noticed, that Django r7411 still generates reduntandt unique indeces when Unique=True, db_index=True and reopened ticked #3030.
Then I updated to r7519 (current head) and discovered, that reduntant unique index is create for OneToOneField (MySQL creates inherent foreign key on UNIQUE column declaration)
Change History (7)
comment:1 by , 17 years ago
comment:2 by , 16 years ago
Keywords: | qsrf-cleanup added |
---|
comment:3 by , 16 years ago
Component: | django.core.mail → Database wrapper |
---|
comment:4 by , 16 years ago
milestone: | → 1.0 |
---|
comment:5 by , 16 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:6 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I've already filled a bug report for the OneToOneField problem here :
http://code.djangoproject.com/ticket/7170