#24447: Migrations do not add a FK constraint for an existing column
----------------------------+---------------------------------------------
Reporter: ganwell | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for checkin
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
----------------------------+---------------------------------------------
Comment (by Markus Holtermann <info@…>):
In [changeset:"283b630d6324c936cbe42d8f0169f056b3ba59c6"]:
{{{
#!CommitTicketReference repository=""
revision="283b630d6324c936cbe42d8f0169f056b3ba59c6"
Fixed #24447 -- Made migrations add FK constraints for existing columns
When altering from e.g. an IntegerField to a ForeignKey, Django didn't
add a constraint.
Backport of f4f0060feaee6bbd76a0d575487682bc541111e4 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24447#comment:8>
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/065.4c15b147eab61025df88b2c37c4fe4ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
