#31703: Name all initial migrations "NNNN_initial".
-------------------------------------+-------------------------------------
     Reporter:  Jon Dufresne         |                    Owner:  Jon
         Type:                       |  Dufresne
  Cleanup/optimization               |                   Status:  closed
    Component:  Migrations           |                  Version:  master
     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:"6f3e3e87ab72eb64dcce8e646f8eea07be6c3b7e" 6f3e3e87]:
 {{{
 #!CommitTicketReference repository=""
 revision="6f3e3e87ab72eb64dcce8e646f8eea07be6c3b7e"
 Fixed #31703 -- Made makemigrations name all initial migrations "initial".

 When the MigrationAutodetector creates more than one initial migration
 in a app, name all initial migrations "initial" rather than the opaque
 "auto_<DATE>_<TIME>" name.

 Initial migrations that have a descriptive name continue to use the
 descriptive name.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31703#comment:7>
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/067.365973449951ae2a6c6cb3c9975840e8%40djangoproject.com.

Reply via email to