#24195: Changing limit_choices_to in a ForeignKey doesn't create a migration
----------------------------------+---------------------------------------
Reporter: Aymeric Augustin | Owner: Adam Bogdał
Type: Bug | Status: closed
Component: Migrations | Version: master
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:"cd2fe829dddb4c8914ac62c93cd6d750a4e9c30c" cd2fe82]:
{{{
#!CommitTicketReference repository=""
revision="cd2fe829dddb4c8914ac62c93cd6d750a4e9c30c"
Fixed #24195 -- Deconstructed the limit_choices_to option of related
fields.
Migrations will now be created for changes to limit_choices_to.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24195#comment:9>
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.07fcb8f8575ac1bb085f8bea27b51139%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
