Migrations crash on SQLite when renaming part of CompositePrimaryKey.

[Mariusz Felisiak]

I've created a sample project that tries to rename a column included in CompositePrimaryKey. Unfortunately, it crashes:

$ python manage.py migrate test_one 0002
...
  File "/django/db/backends/base/schema.py", line 509, in create_model
    sql, params = self.table_sql(model)
                  ^^^^^^^^^^^^^^^^^^^^^
  File "/django/db/backends/base/schema.py", line 290, in table_sql
    constraint_sqls.append(self._pk_constraint_sql(pk.columns))
                                                   ^^^^^^^^^^
  File "/django/utils/functional.py", line 47, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
                                         ^^^^^^^^^^^^^^^^^^^
  File "/django/db/models/fields/composite.py", line 81, in columns
    return tuple(field.column for field in self.fields)
                                           ^^^^^^^^^^^
  File "/django/utils/functional.py", line 47, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
                                         ^^^^^^^^^^^^^^^^^^^
  File "/django/db/models/fields/composite.py", line 77, in fields
    return tuple(meta.get_field(field_name) for field_name in self.field_names)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/django/db/models/fields/composite.py", line 77, in <genexpr>
    return tuple(meta.get_field(field_name) for field_name in self.field_names)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/django/db/models/options.py", line 685, in get_field
    raise FieldDoesNotExist(
django.core.exceptions.FieldDoesNotExist: NewRelease has no field named 'name'

I've attached a sample project. I can prepare a patch in the coming days.

[Mariusz Felisiak]

I've found other migrations that crashes in exactly the same way on SQLite.

[Simon Charette]

Thanks for the report!

The issue likely lies in ProjectState.rename_field and in MigrationAutoDetector.create_renamed_fields which shouldn't generate the AlterField against the composite primary key in the first place.