Change automatic migration naming from date-based to operation-based
Following #31468 and a discussion on django-developers with broad consensus, change the way migrations are automatically named from date-based to operation-based. That is never name migrations based upon the current date (auto_YYYYMMDD) and instead always based on the operations they contain, rather than the current behaviour which uses either style.
Change History
(16)
| Triage Stage: |
Unreviewed → Accepted
|
| Cc: |
Carles Pina Estany added
|
| Owner: |
changed from nobody to Adam Johnson
|
| Patch needs improvement: |
set
|
| Owner: |
changed from Adam Johnson to Manav Agarwal
|
| Patch needs improvement: |
unset
|
| Patch needs improvement: |
set
|
| Patch needs improvement: |
unset
|
| Patch needs improvement: |
set
|
| Patch needs improvement: |
unset
|
| Patch needs improvement: |
set
|
| Patch needs improvement: |
unset
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Type: |
New feature → Cleanup/optimization
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
It looks like a luke-warmish OK on the list, so I guess we should push it forward to review. Thanks Adam.