-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AND criteria doesn't return result if one of the conditions/criteria includes date type field #70
Comments
I was quite surprised by this bug, so I investigated it and I consider it to be a Pulp bug - https://pulp.plan.io/issues/5700. I think that it needs to be fixed in Pulp, because:
I don't think this is actually true (Rajul, can you check?) And although the AND case can be worked around fairly easily by using a dict instead of a list as described here, the same workaround isn't possible for OR. |
Can we drop this in favor of https://pulp.plan.io/issues/5700 ? |
Summary
AND criteria having one of the criteria with the date type field doesn't return any result.
Same date criteria returns a result if used alone(not as part of AND criteria).
returns a result.
But won't return anything with True criteria within AND or any other possibly matching criteria. e.g.
won't return anything (though there are possible matches).
AND criteria works for any other criteria with non-date fields. .e.g.
returns the result.
Issue Type
Steps to reproduce
Create a search request with AND criteria as mentioned in the description involving a date type field and verify with the expected result.
Actual results
search request with AND criteria doesn't return result when one of the conditions includes a date type field.
Expected results
search request with AND criteria should return the expected result even when one of the conditions involve a date type field
OS / Environment
Additional Information
which doesn't return any result. However, if this is modified to
works fine as an AND criteria and returns the expected result.
The text was updated successfully, but these errors were encountered: