Add an explicit id AutoField #142
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…IELD set to BigAutoField
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If a Django application uses the setting
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField', Django will suggest generating the migration0002_alter_template_id, which changes the field type ofTemplate.id.Creating your own migration in the package is not a good idea, as if an official migration 0002 appears in the future, it will cause a conflict. To avoid this, I've added an explicit
idfield of typeAutoField, maintaining backward compatibility and preventing Django from generating a new migration.