#31516: Change automatic migration naming from date-based to operation-based
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Manav
Type: | Agarwal
Cleanup/optimization | Status: closed
Component: Migrations | Version: 3.0
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"99640e24b4c42a9f9b1e02d54aec72c13008276d" 99640e24]:
{{{
#!CommitTicketReference repository=""
revision="99640e24b4c42a9f9b1e02d54aec72c13008276d"
Fixed #31516 -- Improved naming of migrations with multiple operations.
52 gives 60 in total (52 + 5 + 3).
Co-authored-by: Adam Johnson <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31516#comment:16>
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/068.c5eac6777cfbedaee1d31e2b65dd1134%40djangoproject.com.
