#24573: "Unknown column" exception after removing field in migration.
-------------------------------------+-------------------------------------
Reporter: tttomekkk | Owner: MarkusH
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Release blocker | 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
-------------------------------------+-------------------------------------
Comment (by Markus Holtermann <info@…>):
In [changeset:"0cacb8f8ba94b06a78dcdfa22dc406a8a20a7f88" 0cacb8f8]:
{{{
#!CommitTicketReference repository=""
revision="0cacb8f8ba94b06a78dcdfa22dc406a8a20a7f88"
[1.8.x] Fixed #24573 -- Considered new related models for reloading
Thanks tttomekkk for the report.
Backport of b93690c4652a108b4305c0df34509bfc267fd927 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24573#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.354fe824831103cd3b8c84dfa06c1fcf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.