Add a faked column to django_migrations?
- Dominant language
- No language data
- Stars
- 188
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
### Code of Conduct
- [x] I agree to follow Django's Code of Conduct
### Feature Description
Add a `faked` column to the `Migration` model.
### Problem
Sometimes migrations got faked, it might however be useful to know this. Can we add a `faked` column to the migration model which is by default false, but does some bookmarking whether the migration was added to the table because it was migrated, or just faked?
### Request or proposal
request
### Additional Details
_No response_
### Implementation Suggestions
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating Django's Migration model and the migration table-writing path. Determine how the model records applied versus faked migrations, then define the expected default and verify that the stored value distinguishes those cases; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100