#34728: OR operator on queryset does not work as expected
-------------------------------------+-------------------------------------
Reporter: Kbleser | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: queryset OR | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* status: new => closed
* resolution: => needsinfo
Comment:
I'm taking a look at this again. For the sake of clarity, René or the
reporter, could you please paste here the test method (or any other needed
diff) that produce a failure? I've cloned the repo and played a bit with
the existing `find_similar_recipes` and I'm not being able to reproduce
the issue. Thanks!
Regarding:
> If we can't agree here on whether this is a bug or not, should we start
an ML discussion?
I think this may be the best path forward!
>BTW, on Discord, there has been another report about qs1 | qs2 and qs2 |
qs1 not being equivalent, which they should be according to the docs.
Do you have an example or link to the discussion at hand? Perhaps we could
clarify in the docs what "equivalent" mean, in that, given that `|` is not
commutative, it may be the case that the generated `SQL` return different
results but still equivalent, no? :thinking:
--
Ticket URL: <https://code.djangoproject.com/ticket/34728#comment:10>
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/010701898d00ccea-a8577b74-9f4e-44aa-b93c-32fa61e38a37-000000%40eu-central-1.amazonses.com.
