Sorry, I meant to do that. Here's the link to the ticket:
I get an output similar to that of the ticket when I run `./manage makemigrations`:
HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
myapp.MyClass: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
(duplicated about 30 times because I have many such classes)
The primary key for these models has not changed since Django 0.90 and there was no issue in Django 3.1.
It started output HINT messages in Django 3.2 beta 1.
I have the same behaviour in Django 3.2 rc 1.
When I try the suggested workaround from the ticket, i.e.:
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
the migrations files contain the following migrations which I neeed to remove manually:
migrations.AlterField(
model_name='myclass',
name='id',
field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
),
Caram