#31530: Check that CheckConstraint.check and UniqueConstraint.condition don't
span
joins.
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Alexandr Tatarinov):
* needs_better_patch: 0 => 1
Comment:
Is it even possible to handle all cases with Q objects?
As mentioned [https://code.djangoproject.com/ticket/31410#comment:11 in
this comment], custom expressions might be impossible to introspect.
Maybe we can rely on something like `get_source_expressions` to get all
included fields...
--
Ticket URL: <https://code.djangoproject.com/ticket/31530#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/067.77916bd04e0cbe6a000dca0f1dcbf36b%40djangoproject.com.
