Closed wesleyboar closed 7 months ago
I retract my request and bury my concern.
@wesleyboar, this is why you can let this go:
- The migrations for third-party apps are local/transient. They won't be run again.
- The end result is still
BigAutoField
. Trust that Django is smart enough to see that.- If conflicts occur, there is a
… makemigrations --merge <app>
that might help.— https://github.com/TACC/Core-CMS/pull/787#discussion_r1457878445
I am still concerned. Especially given Chat GPT's answer to my question that validates my concern. But, it's Chat GPT answering a complex question, so I shouldn't put much faith in it.
Overview
Avoid migrations by using
AutoField
instead ofBigAutoField
.Background.
Related
Changes
DEFAULT_AUTO_FIELD
fromBigAutoField
toAutoField
Testing
main
branchbuild
new imagestart
new image… makemigrations
deps/python-3.11
chore/collectstatic-on-build
build
new imagestart
new image… makemigrations
UIResultsBigAutoField
AutoField