Opened 10 years ago
Closed 10 years ago
#24337 closed Cleanup/optimization (fixed)
Add documentation about problems with automatic fake-apply of initial migrations
Reported by: | Markus Holtermann | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.7 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
As discussed in #24184, the 1.7 docs about initial migrations should be extended by a paragraph / note / warning about how Django figures out if an initial migration is already applied.
Change History (4)
comment:1 by , 10 years ago
Easy pickings: | set |
---|---|
Triage Stage: | Accepted → Unreviewed |
comment:2 by , 10 years ago
Has patch: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:3 by , 10 years ago
Needs documentation: | unset |
---|---|
Triage Stage: | Accepted → Ready for checkin |
comment:4 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
In 86e9744593c6688849da8adc26bf19e51404c113: