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.
Activity
- All
- Comments
- History
- Activity
- Transitions
- Commits
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.
Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.
