Opened 2 months ago

Last modified 2 months ago

#28784 assigned Cleanup/optimization

Clarify migrate --fake documentation

Reported by: Ramez Kabbani Owned by: gagan trivedi
Component: Documentation Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no


migrate documentation implies that running migrate --fake on a specific migration toggles its applied status (applied => unapplied and vice versa). The reality is that one needs to run migrate --fake on the preceding migration to mark the migration as unapplied.

Change History (3)

comment:1 Changed 2 months ago by Tomer Chachamu

Triage Stage: UnreviewedAccepted

Agreed it could be clearer.

comment:2 Changed 2 months ago by tothegump

What about:
Tells Django to mark the migrations before and including this <migrationname> as having been applied, meanwhile mark the migrations after this <migrationname> as having been unapplied?

But it is not concise.

comment:3 Changed 2 months ago by gagan trivedi

Owner: changed from nobody to gagan trivedi
Status: newassigned
Note: See TracTickets for help on using tickets.
Back to Top