chore: Explicitly set default auto field #108
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://docs.djangoproject.com/en/5.0/ref/settings/#default-auto-field
Users may set
DEFAULT_AUTO_FIELD
todjango.db.models.BigAutoField
in settings.In that case, it will create an additional migration file which updates
APIRequestLog
table id toBigAutoField
.And it's causing problem during the migration in each deployment and testing with
tox
.If we explicitly set
default_auto_field
in app config, we can avoid unexpected migration.