37👍
✅
After raised the ticket and got closed due to duplication, finally found the answer:
This is by design. There are several reasons, not least of which for me that datamigrations at points in history need to have a full accurate representation of the models, including all their options not just those which affect the database.
Reference:
4👍
From Django docs:
Django will make migrations for any change to your models or fields – even options that don’t affect the database – as the only way it can reconstruct a field correctly is to have all the changes in the history, and you might need those options in some data migrations later on (for example, if you’ve set custom validators).
Reference:
- [Django]-Deploying Google Analytics With Django
- [Django]-ImproperlyConfigured: You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings
- [Django]-How can I handle Exceptions raised by dango-social-auth?
Source:stackexchange.com