#31516: Change automatic migration naming from date-based to operation-based
-------------------------------------+-------------------------------------
Reporter: Adam | Owner: nobody
(Chainz) Johnson |
Type: New | Status: assigned
feature |
Component: | Version: 3.0
Migrations |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Following #31468 and a [https://groups.google.com/d/msg/django-
developers/Bmcd779Wdl4/mlQRVNVgAQAJ 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/31516>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.3f9276bb711fc1d018b1a3f8cca80c16%40djangoproject.com.
