#25317: Altering a field to ForeignKey does not create index
-------------------------------+--------------------------------------
Reporter: synotna | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by shaib):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
Why should one be created? If it was a !OneToOneField, it should already
have an index, and I see nothing there to drop it.
I suppose you came to the conclusion that something was wrong because
something failed for you; it would be more useful to describe the problem
you encountered and the process that led you to the conclusion that the
behavior was wrong (but, the proper place to do so would be a users forum
like the [https://groups.google.com/d/forum/django-users django-users
group]).
I am closing the ticket as invalid based on the info given; feel free to
reopen (and explain) if I've misunderstood, or to open a separate ticket
if appropriate.
--
Ticket URL: <https://code.djangoproject.com/ticket/25317#comment:1>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.07371fcbc9ce421c691fb950ff4f1c78%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
