Closed rjmagley closed 1 year ago
Creating a brand-new Django 4.2 project has this hanging out in settings.py:
# https://docs.djangoproject.com/en/4.2/ref/settings/#default-auto-field
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
Setting this probably fixes the warnings.
I forgot when exactly I made this change, but the DEFAULT_AUTO_FIELD
is in settings.py now, so that's done.
Lots of warnings in this vein pop up when starting a local environment for testing:
I suspect either something went weird with the migrations at some point, or a Django update changed how models are handled. The tables in the DB are all properly getting the proper
id
field added to them when migrations are made, so this isn't a big deal.