#30750: Add support for check constraints on MySQL 8.0.16+.
-------------------------------------+-------------------------------------
Reporter: felixxm | Owner: Hasan
| Ramezani
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: MySQL, check | Triage Stage: Accepted
constraints |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Hasan Ramezani):
* has_patch: 0 => 1
Comment:
@felixxm, I fixed the [https://github.com/django/django/pull/11743/files
#diff-888b45a0a8f38ee67e8d22403cf994dbL1133 test_alter_db_table_case
test].
The problem was that the table belongs to the `Author` model couldn't be
dropped because when the test rename table to the uppercase name, the
`_meta.db_table` has the old name(lowercase name).
So I added another rename to return the table to the original name.
--
Ticket URL: <https://code.djangoproject.com/ticket/30750#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.de927df3e049c9e8cb80842567f8393a%40djangoproject.com.
