#30350: CheckConstraint repeatedly deleted and re-added
-------------------------------------+-------------------------------------
Reporter: Sigurd Ljødal | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by felixxm):
In check constraints you can use `range` lookup and it works fine, e.g.
{{{#!python
models.CheckConstraint(
check=models.Q(month__range=[1, 13]),
name='check_valid_month',
)
}}}
also casting an iterator to a list works good, e.g.
{{{#!python
models.CheckConstraint(
check=models.Q(month__in=list(range(1, 13))),
name='check_valid_month',
)
}}}
so in this case iterator is an issue. I would check later if this can be
easily fix and if not we should document this limitation.
--
Ticket URL: <https://code.djangoproject.com/ticket/30350#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/064.82858f5f431f26f2870a8d1dec5d322f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
