Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#34529 closed Bug (fixed)

Squashing migrations with Meta.index_together -> indexes transition should remove deprecation warnings.

Reported by: Mariusz Felisiak Owned by: Mariusz Felisiak
Component: Migrations Version: 4.2
Severity: Release blocker Keywords:
Cc: Simon Charette, David Sanders Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Squashing migrations with Meta.index_together -> Meta.indexes transition should remove deprecation warnings. As far as I'm aware, it's a 4.2 release blocker because you cannot get rid of the index_together deprecation warnings without rewriting migrations, see comment.

Change History (4)

comment:1 by Simon Charette, 3 years ago

Triage Stage: Unreviewed → Accepted

comment:2 by Mariusz Felisiak, 3 years ago

Has patch: set

​PR

comment:3 by GitHub <noreply@…>, 3 years ago

Resolution: → fixed
Status: assigned → closed

In 8e2460d5:

Fixed #34529, Refs #34525 -- Reduced index operations with Meta.indexes/index_together when optimizing migrations.

This makes squashing migrations an available path for changing
Meta.index_together, which is deprecated, to Meta.indexes.

Follow up to f81032572107846922745b68d5b7191058fdd5f5.

comment:4 by Mariusz Felisiak <felisiak.mariusz@…>, 3 years ago

In 290fd5ec:

[4.2.x] Fixed #34529, Refs #34525 -- Reduced index operations with Meta.indexes/index_together when optimizing migrations.

This makes squashing migrations an available path for changing
Meta.index_together, which is deprecated, to Meta.indexes.

Follow up to f81032572107846922745b68d5b7191058fdd5f5.

Backport of 8e2460d599aec95f8cfe514d3cc8acdd4ca4b1fb from main.

Note: See TracTickets for help on using tickets.
Back to Top