#34217: Migration removing a CheckConstraint results in ProgrammingError using
MySQL < 8.0.16.
----------------------------+---------------------------------------------
Reporter: Max Fisco | Owner: Bhuvnesh
Type: Bug | Status: closed
Component: Migrations | Version: 4.1
Severity: Normal | 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 GitHub <noreply@…>):
In [changeset:"16c966ff7fc9ce01e3afd87ef2af55859cadb587" 16c966ff]:
{{{
#!CommitTicketReference repository=""
revision="16c966ff7fc9ce01e3afd87ef2af55859cadb587"
Refs #30060, Refs #34217 -- Made SchemaEditor not generate SQL for
CheckConstraint if not supported.
The new logic mirrors the logic in SchemaEditor._delete_check_sql()
added in 68ef274bc505cd44f305c03cbf84cf08826200a8.
Thanks Tim Graham for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34217#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701867fe842b3-bb4f4911-d5c9-4798-9059-265e3235935f-000000%40eu-central-1.amazonses.com.
