Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Performing exclude with in doesn't always work as expected. #16

Closed
notanumber opened this issue Aug 20, 2009 · 3 comments
Closed

Performing exclude with in doesn't always work as expected. #16

notanumber opened this issue Aug 20, 2009 · 3 comments
Labels
Defect

Comments

@notanumber
Copy link
Owner

It appears as though performing exclude with in prior to filtering results does not result in the same set as filtering first, then performing exclude.
@notanumber
Copy link
Owner Author

SHA 7c00117 should fix this. A new version of the SearchQuery.build_query method has been implemented that should better account for all of the various filters and types.

@notanumber
Copy link
Owner Author

Appears as though this isn't quite right yet. The query generation is working as expected but the result set isn't the same depending on if the exclude is performed first or last.

eg.

"java AND NOT id:1 NOT id:2" doesn't give the same results as "NOT id:1 NOT id:2 AND java"

@notanumber
Copy link
Owner Author

As far as I can tell, this has been fixed by the 1.1 refactor.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@notanumber