Test reworking migration for mysql/postgresql

evennia/typeclasses/migrations/0017_use_index_instead_of_index_together_in_tags.py

@@ -9,8 +9,11 @@ class Migration(migrations.Migration):
         ("typeclasses", "0016_alter_attribute_id_alter_tag_id"),
     ]
 
-    operations = [
+    def get_operations(self, app_labels, schema_editor):
-        # First create the index with the old name that Django expects
+        """Return database-specific operations"""
+        if schema_editor.connection.vendor == "sqlite":
+            # For SQLite, we know the two-step process works
+            return [
                 migrations.AddIndex(
                     model_name="tag",
                     index=models.Index(
@@ -18,10 +21,22 @@ class Migration(migrations.Migration):
                         name="typeclasses_tag_db_key_db_category_db_tagtype_db_model_idx",
                     ),
                 ),
-        # Then rename it to the new name
                 migrations.RenameIndex(
                     model_name="tag",
                     new_name="typeclasses_db_key_be0c81_idx",
                     old_fields=("db_key", "db_category", "db_tagtype", "db_model"),
                 ),
             ]
+        else:
+            # For other databases, create the index directly with its final name
+            return [
+                migrations.AddIndex(
+                    model_name="tag",
+                    index=models.Index(
+                        fields=["db_key", "db_category", "db_tagtype", "db_model"],
+                        name="typeclasses_db_key_be0c81_idx",
+                    ),
+                ),
+            ]
+
+    operations = []  # Will be populated at runtime by get_operations()