Which is a waste of resources and makes it an easy attack vector.
I just ran the same query, looked for "Q" in post titles for user Lurker17, whole db regardless of subverse, no time constraints (all time).
"119 found, 0.009 secs" on Searchvoat.co
Seems like a reasonable search execution time? Not a big deal. I can live without 1 char search.
Regardless, thanks for the enhanced search features, they will come in handy.
for user Lurker17, whole db regardless of subverse
Not the whole DB, only within your posts.
Not the whole DB, only within your posts.
Yeah, that's what I meant; my posts only, title only, any subverse (ie "within the whole db"). My db nomenclature may not be quite up to snuff, it's been years, db's were not my forte ... only worked with them on an infrequent as needed basis ~40 years ago.
It was essentially the same search criteria I attempted on a whim in my example on POAL (but I was stymied by the > 1 char search criteria rule). I specified only @Lurker17 posts, title only search for single char "Q", any subverse in POAL, at any time. I replicated that same search criteria on Searchvoat.co, also included nsfw posts.
I understand an all user, all subverse, all content search for a single character is nuts, but I had whittled my query down to a title search only, @Lurker17 posts only, any subverse. I have ~17646 posts to date on POAL.
I do understand why you aren't allowing 1 char searches because it would be a waste of cpu - unless the query criteria had reduced the search to a manageable size like one user, titles only. Writing the code to allow this exception cases with reduced search criteria would probably not be worthwhile, 99.99% of all searches will involve > 1 char. I'll get by.