#23861: Fields referenced in migrations cannot be (re)moved, even if migrations
have been squashed
-------------------------------------+-------------------------------------
Reporter: spookylukey | Owner: timgraham
Type: Bug | Status: closed
Component: Migrations | Version: master
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
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"c87ee41954737869e6026d6fb12394ec4f79d50a"]:
{{{
#!CommitTicketReference repository=""
revision="c87ee41954737869e6026d6fb12394ec4f79d50a"
Fixed #23861 -- Added an API to deprecate model fields.
Thanks Markus Holterman and Berker Peksag for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23861#comment:18>
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/069.000dc1dd870424224c8a421071478ff2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
