#34856: Running tests with historical migrations that contain index together
fails
with TypeError.
-------------------------------+--------------------------------------
Reporter: Sage Abdullah | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Normal | Resolution:
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 Sage Abdullah):
To add, the [https://docs.djangoproject.com/en/dev/releases/4.2/#index-
together-option-is-deprecated-in-favor-of-indexes 4.2 release notes] do
say the following though:
> Next, consider squashing migrations to remove `index_together` from
historical migrations.
> 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. Use
`AddIndex` and `RemoveIndex` operations instead.
But with the problem in this ticket, it seems squashing the migrations
will be mandatory?
--
Ticket URL: <https://code.djangoproject.com/ticket/34856#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ab30c5fd6-8dfa6140-d3c1-4537-a8ff-71905e606d18-000000%40eu-central-1.amazonses.com.
