#31720: Better documentation and defaults for BoolOr and BoolAnd
-------------------------------------+-------------------------------------
Reporter: Alex Scott | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* owner: (none) => nobody
* needs_docs: 0 => 1
* type: Uncategorized => Cleanup/optimization
* component: contrib.postgres => Database layer (models, ORM)
* stage: Unreviewed => Accepted
Comment:
A patch for both documentation and explicit `output_field` for `BoolOr`
and `BoolAnd` would be welcome. The issue you're experiencing here is
likely due to the fact `Q` and `WhereNode` are marked `conditional=True`
but don't set `output_field = models.BooleanField()` and thus the default
behavior of `Expression._resolve_output_field` cannot be leveraged.
Are you interested in submitting a PR with these improvements?
--
Ticket URL: <https://code.djangoproject.com/ticket/31720#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.88c59c454eb21c8fdbc414a933e35cf1%40djangoproject.com.
