#30593: Add support for check constraints on MariaDB 10.2+.
-------------------------------------+-------------------------------------
Reporter: felixxm | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: MariaDB, | Triage Stage: Accepted
constraint, check |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Hasan Ramezani):
* needs_better_patch: 0 => 1
* has_patch: 0 => 1
Comment:
3 tests fail:
* `introspection.tests.IntrospectionTests.test_get_constraints`
* `schema.tests.SchemaTests.test_check_constraints`
*
`schema.tests.SchemaTests.test_remove_field_check_does_not_remove_meta_constraints`
The `information_schema.key_column_usage` table, does not contain `CHECK`
constraints records. we can find them in
`information_schema.table_constraints` table.
The problem is that records in `information_schema.table_constraints` do
not have `column_name` and we have to add them to constraints with an
empty list of columns [https://github.com/django/django/pull/11566/files
#diff-ed5c74bb534df74e38bc62e79c84fa12R194].
Those 3 tests fail because of the above-mentioned problem.
Any idea?
--
Ticket URL: <https://code.djangoproject.com/ticket/30593#comment:1>
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/065.538ae320d21aa8e077b946b1b7429fcb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
