#28731: Passing an empty Q() to a When inside a Case causes an OperationError
-------------------------------------+-------------------------------------
Reporter: Tom van Bussel | Owner: Tim
| Martin
Type: Bug | Status: assigned
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Martin):
I don't think it's explicitly deprecated, we'd need to have a discussion
on the mailing list to get consensus on that.
However, I think reporting an explicit "empty `Q()` object not supported"
error is much better than sending invalid SQL to the database and getting
it rejected. I don't think the DB layer should ever send invalid SQL.
--
Ticket URL: <https://code.djangoproject.com/ticket/28731#comment:12>
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/068.0a37bbd07efad8e1d57dacffd564e171%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
