#30591: MySQL: 1215 - "Cannot add foreign key constraint" when altering type of
unique field referenced by ForeignKey.
----------------------------------+--------------------------------------
Reporter: Cornelis Poppema | Owner: Adnan Umer
Type: Bug | Status: assigned
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by GitHub <noreply@…>):
In [changeset:"579909a13feb958f75d1d77e9995cef8f2b9c2a3" 579909a1]:
{{{
#!CommitTicketReference repository=""
revision="579909a13feb958f75d1d77e9995cef8f2b9c2a3"
Refs #30591 -- Fixed introspection of check and unique column constraints
on MariaDB.
Unnamed unique and check columns constraints have the same name as
a column. Ensure uniqueness by using custom names.
Thanks Adnan Umer for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30591#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.f401fcd686ca4ea65c6168eced7c6659%40djangoproject.com.
