#26926: Dual index migration bug?
----------------------------+--------------------
Reporter: Vaal | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------
Example:
1) Added new field to model
x_index = models.BooleanField(default=True, db_index=True, unique=True)
There is an unnecessary index. But the conditions of the situation.
2) Create and run the migration.
In the database this field will have only one index - unique.
3) Change the field.
x_index = models.BooleanField(default=True, db_index=True)
Remove the unique index.
4) Create and run the migration.
Now, this field doesn't have of any indexes in database.
--
Ticket URL: <https://code.djangoproject.com/ticket/26926>
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/047.2f2b7df1893c8c206b8811589075750a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
