Is boolean search important?
Should boolean search stay?
Yes, it should stay |
![]() ![]() ![]() |
It should stay if there's no technical problem keeping it (performance, maintenance cost, etc) |
![]() ![]() ![]() |
No, it is old-school, bloaty, not useful |
![]() ![]() ![]() |
Unsure |
![]() ![]() ![]() |
Posted
#6685
(In Topic #1731)

Site director

Eventually things moved to a much simpler phrase based search. The search phrase was broken down to keywords and an algorithm would rank results based on how well it matched the keywords (basically) - like a fuzzy AND query between the keywords.
MySQL full text search works in the newer way, although you can also force a boolean search mode.
Composr supports both modes.
I want to know if nowadays anybody cares about, or expects, boolean search support.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Posted

Standard member

I cannot remember the last time I used the Boolean search.
1 guest and 0 members have just viewed this.