Project

Profile

Help

Task #6703

closed

Document that users should not run makemigrations but file a bug instead

Added by ttereshc almost 4 years ago. Updated almost 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Quarter:
Q2-2021

Description

Users should not run django-admin makemigrations because if there is any new migration created, at minimum, it will affect the upgrade in the future.

Cases when django-admin makemigrations produces a new migration:

  • users modified code (models)
  • there is a bug
    • some migration is not committed
    • existing migrations are not in sync with models, aka incorrect existing migrations

Document that users should never run makemigrations if they are not making some changes on purpose (in this case they are conscious that they will be on their own with the upgrade.), and file a bug if django prompts them to run something like that.

Also available in: Atom PDF