Opened 11 years ago
Closed 11 years ago
#22032 closed Cleanup/optimization (fixed)
Document settings.MIGRATION_MODULES
Reported by: | Baptiste Mispelon | Owned by: | gregchapple |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Release blocker | Keywords: | migrations nlsprint14 |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
There's no mention of this new setting in the documentation.
From what I understand, it's a way to override where Django can find migrations for a given app.
It's a dictionary where keys are the names of applications and the values are the name of the module (inside the app) where the migrations reside.
Change History (8)
comment:1 by , 11 years ago
Severity: | Normal → Release blocker |
---|
comment:3 by , 11 years ago
At the very least, it should be present in the full list of settings [1].
A mention in the migrations documentation itself would be a good idea too though I'm not sure which section is the most appropriate for that.
The second section ("Two commands") says that "the migration files for each app live in a “migrations” directory inside of that app [...]" so maybe a quick mention of the setting at this point would be best.
What do you think?
comment:4 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:5 by , 11 years ago
Keywords: | nlsprint14 added |
---|
comment:6 by , 11 years ago
Added a patch in this pull request https://github.com/django/django/pull/2352
comment:7 by , 11 years ago
Has patch: | set |
---|
comment:8 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Should this reside in https://docs.djangoproject.com/en/dev/topics/migrations/#adding-migrations-to-apps ?