#34856: Running tests with historical migrations that contain index together
fails
with TypeError.
-------------------------------+--------------------------------------
Reporter: Sage Abdullah | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: dev
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
-------------------------------+--------------------------------------
Comment (by Tim Graham):
And the release notes say, "The `AlterIndexTogether` migration operation
is now officially supported only for pre-Django 4.2 migration files. For
backward compatibility reasons, it’s still part of the public API, and
there’s no plan to deprecate or remove it, but it should not be used for
new migrations. "
I'm not immediately seeing what purpose it serves if it crashes (see
#35679). I think removing an index, e.g. `AlterIndexTogether("Pony",
None)`, still works, but I'm not sure this provides sufficient value to
keep it around.
--
Ticket URL: <https://code.djangoproject.com/ticket/34856#comment:5>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070191815da596-88c969c3-8a2f-405a-9462-bce397c2a62b-000000%40eu-central-1.amazonses.com.
