Closed Zoidmania closed 2 years ago
From the docs:
Starting with Django 3.2, the built-in ID/PK field type is BigAutoField.
BigAutoField
id = models.BigAutoField(primary_key=True) ... In older versions, auto-created primary key fields were always AutoFields.
id = models.BigAutoField(primary_key=True)
This causes a new migration requirement for this package:
operations = [ migrations.AlterField( model_name='event', name='id', field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'), ), migrations.AlterField( model_name='eventcounter', name='id', field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'), ), ]
The initial model/migration will need to be updated to use BigAutoField, or you can set default id field type in the app config.
How do you want to handle this? Are pull requests preferable?
Hmm, well whatever we do, hopefully it can be backwards compatible. Open to pull requests.
Backward compatible to which Django version(s)?
Maybe 2.2, considering channels dependency?
channels
From the docs:
Starting with Django 3.2, the built-in ID/PK field type is
BigAutoField
.This causes a new migration requirement for this package:
The initial model/migration will need to be updated to use BigAutoField, or you can set default id field type in the app config.
How do you want to handle this? Are pull requests preferable?