Details
-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: Current Version
-
Fix Version/s: None
-
Component/s: SIO2 Project Website and Infrastructure
-
Labels:None
Description
Because of the change in Django 3.2, when defining a model, if no field in a model is defined with primary_key=True an implicit primary key is added. The type of this implicit primary key can now be controlled via the DEFAULT_AUTO_FIELD setting and AppConfig.default_auto_field attribute. No more needing to override primary keys in all models.
To avoid unwanted migrations in the future, configure it on a per-app basis by adding default_auto_field = 'django.db.models.AutoField' in all AppConfig classes.
To avoid unwanted migrations in the future, configure it on a per-app basis by adding default_auto_field = 'django.db.models.AutoField' in all AppConfig classes.
https://gerrit.sio2project.mimuw.edu.pl/3824
SIO-2501Auto-created primary key used when not defining a primary key type warningi Attribute default_auto_field = 'django.db.models.AutoField' to point to a subclass of AutoField added in all classes that inherit from AppConfig.Change-Id: Ibc19cc9a2db265391dae3646c6ec82b48356e246