#34217: Migration removing a CheckConstraint results in ProgrammingError using
MySQL < 8.0.16.
----------------------------+------------------------------------
Reporter: Max Fisco | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 4.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:2 Max Fisco]:
> Hi Mariusz,
>
> Thanks for the quick response! As far as the patch goes, I'd love to
contribute (first time reporting a bug) but I think it'd be better to let
someone else pick it up.
>
> I tried to by following along with
[https://docs.djangoproject.com/en/dev/intro/contributing/#writing-your-
first-patch-for-django]; however, I'm having some difficulty figuring out
how to just get the tests to run using MySQL 5.7 in the first place 😕.
>
> {{{
>
> File "/Users/maxwellfisco/django-
fork/django/django/db/backends/base/base.py", line 214, in
check_database_version_supported
> raise NotSupportedError(
> django.db.utils.NotSupportedError: MySQL 8 or later is required (found
5.7.40).
> }}}
Django 4.2 no longer supports MySQL < 8, so you need to use MySQL 8 to
test against the current `main` branch.
--
Ticket URL: <https://code.djangoproject.com/ticket/34217#comment:3>
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/010701852dbb606a-6889b043-8f7f-43b1-b58e-8d4a18ce672a-000000%40eu-central-1.amazonses.com.
