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.

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

make a way to combine search query nodes with an OR relationship #8881

Closed
mixxxbot opened this issue Aug 23, 2022 · 3 comments · Fixed by #12061
Closed

make a way to combine search query nodes with an OR relationship #8881

mixxxbot opened this issue Aug 23, 2022 · 3 comments · Fixed by #12061

Comments

@mixxxbot
Copy link
Collaborator

mixxxbot commented Aug 23, 2022

Reported by: Be-ing
Date: 2017-06-14T19:07:14Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1697983


Currently, every search term typed into the library query field is combined with AND relationships. It would be nice if there was a way to combine nodes with an OR relationship too. For example:
(artist:foo | artist:bar)
would match tracks that have an artist field matching either "foo" or "bar".

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2017-06-14T20:17:08Z


I think we should follow the Google syntax:
https://support.google.com/websearch/answer/2466433?hl=en
and use OR and AND

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2017-06-14T20:31:07Z


Yeah, case sensitive "OR" would be easier to type while mixing.

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2017-12-28T08:41:56Z


I think I have taken up enough for myself for the 2.2 release with the effects system improvements. Does anyone else want to volunteer for this? Uwe? If not, let's remove it from the 2.2 milestone.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@daschuer daschuer added this to the 2.5.0 milestone Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants