#28731: Passing an empty Q() to a When inside a Case causes an OperationError -------------------------------------+------------------------------------- Reporter: Tom van Bussel | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 1.11 (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 Tom van Bussel): Replying to [comment:2 Tomer Chachamu]: > What did you expect to be the value of `x[0].test_name`? I expected `x[0].test_name == True` to hold. > We don't have any documentation on how a `Q(**kwargs)` object behaves when `len(kwargs) == 0`, and we have no tests for it. Perhaps it should be raising an exception (or initially a deprecation warning). Currently `TestModel.objects.filter(Q()).all() == TestModel.objects.all()`, so it would be nice if that behavior is matched everywhere. -- Ticket URL: <https://code.djangoproject.com/ticket/28731#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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/068.7710073cc90cf16890ad89cec6e079b4%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.