#26624: Error when running sqlmigrate after dropping index (of index_together)
without actually migrating
-------------------------------------+-------------------------------------
Reporter: Akshesh Doshi | Owner: <default>
Type: Bug | Status: closed
Component: Migrations | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: sqlmigrate db- | Triage Stage: Accepted
indexes |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
> index_together is ​discouraged, but I don't see anywhere that it's been
deprecated, and it will exist in migrations indefinitely.
My bad, `index_together` is definitely deprecated, whereas
`unique_together` is merely discouraged. I confused them because I came
here from a duplicate for `unique_together`: #31834. comment:7 also deals
with `unique_together`.
I think we ought to undo the wontfix. Not sure whether to retitle this
ticket for `unique_together` or start a new one.
--
Ticket URL: <https://code.djangoproject.com/ticket/26624#comment:8>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070196f29de454-ad137163-8ef5-4f25-a89a-1ac4d6c76fa1-000000%40eu-central-1.amazonses.com.
