#24264: foreign key constraint error migrating integer pk to CharField
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: MarkusH
Type: Bug | Status: closed
Component: Migrations | Version: 1.8alpha1
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:"8ca0eb2af70b7fbfd9689553d40ef6023433f94e"]:
{{{
#!CommitTicketReference repository=""
revision="8ca0eb2af70b7fbfd9689553d40ef6023433f94e"
[1.8.x] Refs #24264 -- Added failing test case for updating a FK when
changing a PK
When the primary key column is altered, foreign keys of referencing
models must be aware of a possible data type change as well and thus
need to be re-rendered.
Thanks Tim Graham for the report.
Backport of cc22b009e05456e3d9cf3c152fe47fa27772be5e from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24264#comment:11>
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.ac3d0bfdfb2ce4cbfc96794815325761%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
