#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
--------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"6be255a22a32a58a96b8d1c67485e92b49817b9f" 6be255a2]:
{{{
#!CommitTicketReference repository=""
revision="6be255a22a32a58a96b8d1c67485e92b49817b9f"
[1.10.x] Fixed #24650 -- Documented how to change an unmanaged model to
managed.
Backport of 80c03b06ad1461c1a07091806dc0414a4e98905e from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24650#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 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.9178c716d9a67980b43b1dba69adc7c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
