Why doesn't django dumpdata include the django_migrations table? -


django dumpdata (with no app specified) dumps tables of installed apps output file. realized did not include django_migrations table. checked other django tables, included specified in installed_apps setting follows:

'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.messages', 'django.contrib.staticfiles', 

now, curious, why wasn't django_migrations table not dumped. rationale seems when create new database , migrate, generated , populated data automatically. correct? if so, second question there way dump (as up)? new django , trying new things might break table. handy have up.

the django_migrations table lives outside conventional django machinery, that's why wasn't included (per @knbk).

as long backup apps, there no need backup migrations table. can delete app tables , re-migrate everything. while @ it, may want squash migrations @ point either using squash command or deleting migrations , creating scratch.


Comments

Popular posts from this blog

Magento/PHP - Get phones on all members in a customer group -

php - .htaccess mod_rewrite for dynamic url which has domain names -

Website Login Issue developed in magento -