#26114: Removing Meta.db_table generates migration with wrong rename in comment
(None)
----------------------------+------------------------------------
Reporter: dvinegla | Owner: PREM1980
Type: Bug | Status: closed
Component: Migrations | Version: 1.9
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 Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"5da7e3f7fd24381195e557d807118130ddbc5152" 5da7e3f]:
{{{
#!CommitTicketReference repository=""
revision="5da7e3f7fd24381195e557d807118130ddbc5152"
Fixed #26114 -- Fixed AlterModelTable.describe() if db_table is None.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26114#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/066.921e7e39c8e6e300c36cdd867a0ed3a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
