Fix regressions from Django 3.2.

Review Request #11580 — Created April 6, 2021 and submitted

Information

Django Evolution
release-2.x

Reviewers

Django 3.2 was just released, and triggered some regressions with
Postgres and for index generation.

The index generation issue was just a matter of converting a positional
argument to a keyword argument. This change was backwards-compatible to
all supported versions of Django.

The Postgres issue was caused by the Postgres backend requiring access
to a field's model when renaming a field. We weren't setting the model
on these fields before, and there was no good reason for this. We now
set the model, fixing this issue.

Unit tests pass on all supported versions of Django, and with all
database types.

Summary ID
Fix regressions from Django 3.2.
Django 3.2 was just released, and triggered some regressions with Postgres and for index generation. The index generation issue was just a matter of converting a positional argument to a keyword argument. This change was backwards-compatible to all supported versions of Django. The Postgres issue was caused by the Postgres backend requiring access to a field's model when renaming a field. We weren't setting the model on these fields before, and there was no good reason for this. We now set the model, fixing this issue.
a6b0243304aeba745bc007e4e0c71b8158d5e23e
david
  1. Ship It!
  2. 
      
chipx86
Review request changed
Status:
Completed
Change Summary:
Pushed to release-2.x (1e35b69)