#24650: Migration changing db_table and managed not creating new table
--------------------------------------+------------------------------------
     Reporter:  duduklein             |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  closed
    Component:  Documentation         |                  Version:  1.8
     Severity:  Normal                |               Resolution:  fixed
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  1                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by GitHub <noreply@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"80c03b06ad1461c1a07091806dc0414a4e98905e" 80c03b06]:
 {{{
 #!CommitTicketReference repository=""
 revision="80c03b06ad1461c1a07091806dc0414a4e98905e"
 Fixed #24650 -- Documented how to change an unmanaged model to managed.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/24650#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c21aaf97198df31f2d84da3400336a25%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to