From 2ee6ca6d35f667c54cba7efacccee3b9f178a6e7 Mon Sep 17 00:00:00 2001 From: Andrés Reverón Molina Date: Mon, 16 Dec 2024 13:54:51 +0100 Subject: [5.1.x] Fixed #34856 -- Fixed references to index_together in historical migrations. While AlterUniqueTogether has been documented to be still allowed in historical migrations for the foreseeable future it has been crashing since 2abf417c815c20 was merged because the latter removed support for Meta.index_together which the migration framework uses to render models to perform schema changes. CreateModel(options["unique_together"]) was also affected. Refs #27236. Co-authored-by: Simon Charette Backport of b44efdfe543c9b9f12690b59777e6b275cb08103 from main. --- docs/releases/5.1.5.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/releases/5.1.5.txt b/docs/releases/5.1.5.txt index af0dab545c..2dfe283e00 100644 --- a/docs/releases/5.1.5.txt +++ b/docs/releases/5.1.5.txt @@ -9,4 +9,5 @@ Django 5.1.5 fixes several bugs in 5.1.4. Bugfixes ======== -* ... +* Fixed a crash when applying migrations with references to the removed + ``Meta.index_together`` option (:ticket:`34856`). -- cgit v1.3