Set default for AutoFields to BigAutoField
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 58/100
Research direction
Start with the Django default-auto-field setting documentation linked in the issue, then locate pulpcore's Django configuration. The work is complete when Django uses BigAutoField instead of AutoField by default and the existing PULP-890 problem is prevented.
Written by the indexing model from the issue text.
Description
We want to avoid the problem encountered in PULP-890 in the future. To do so, we need to teach Django to use BigAutoField instead of AutoField - see https://docs.djangoproject.com/en/4.2/ref/settings/#default-auto-field
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 95
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pulp/pulpcore
-
Issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Feature
-
Issue Triage-Needed
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
ArtifactFileField.pre_save spuriously rejects uploads named 'artifact*' when MEDIA_ROOT is empty Open
Difficulty 3/5 1-2 days Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100