Missing migrations for core modules
dekoza opened this issue · comments
Issue Summary
It seems there are changes in ocar core models that are not reflected in migrations. This results in my app trying to create those when I run ./manage.py makemigrations
This can be confusing for new users and even cause errors in some scenarios (for example during deployment).
Steps to Reproduce
Follow the tutorial from documentation creating frobshop. After done with configuration, runing ./manage.py migrate complains about missing migrations and running ./manage.py makemigrations creates them for build-int oscar modules.
After some investigation it turns out, they just modify the id field on each model to use BigAutoField.
I think there should be some information in the docs about this plus a step on how to create them inside your project (for example if you want to set different field type for ids).
Technical details
- Python version: 3.11.5
- Django version: 3.2.21
- Oscar version: 3.2
Nevermind, I just found this fixed in Oscar 3.2.1a0.