That’s just fucking classic.
It is a search, one that returned too many results, thus the error.
Why you chose to Pit that instead of the fact that we also have to wait after a search that produces zero results is beyond me.
Not always. I got one of these yesterday, got an error, reproduced the same search 300 seconds later with an actual result (nowhere near the search limit–I think it was maybe 2 pages.)
That’s the one that kills me!
I always thought that the issue regarding searches (from the management standpoint) was it taxed the servers, that searches themselves put a strain on it. If so, then it wouldn’t matter that the search produced zero results, it still would have caused the same level of strain, right? I mean if I look through 10,000 files, I’ve still looked through 10,000 files, regardless of how many ‘finds’ I got.
Yeah, that’s a real pisser. You mistype a word, and right as you hit ‘submit’ you realize that you’ve spelled “Sony” as “Sorny,” meaning you’ll get bupkis for results. Its tempting to have a sockpuppet just for those purposes. (Which, unfortunately, is against the rules, so totally not worth it.)
Yes, but the Dope’s servers are infamous for failing under the slightest bit of load.
Granted. But if whole idea about limiting searches in the first place was to reduce the load, then the number of searches is the issue. So I don’t get the whole “yea, and if my search reveals bupkiss hows come I gotta wait then, huh” gig.
Because at least if the search spits outs zillions of results, you can wade through those while waiting for the clock to run out to do your next one.
OK I wasn’t clear. I “get” why it’s annoying. Anytime you have to wait for what you want, it’s annoying. What I dont “get” is Lute’s response
(that everyone chimed in on), which seems point out that having to wait for another search even when it supplied no answers was ‘beyond (him)’
There’s a database I have to use for work. I ‘pay’ for each search. Even when the search turns up bupkiss. Even when the search turns up bupkiss 'cause I did a typo, or some other thing.
Same issue - you’re ‘paying’ for the search itself, not the results.
The real annoyance for me is when it doesn’t do a search because I goofed, something like not putting in enough letters, say. There’s no delay. It immediately says that I didn’t input something right and the search wasn’t run.
And then I have to wait five minutes to fix it.
Yahbut, we’re Dopers, we’re supposed to bitch! Its like a rule or something! 
I’m not absolutely sure, but I don’t think that’s true. If I search and find no results, I’ve trawled the index, not the whole database.
A search that returns results does the same - it trawls the index - plus the server then has to retrieve the resulting thread titles and enough text from the first post for the mouseover preview, and it has to format those results for your browser.
part of the complaint is that before the update you didn’t have to wait 300 sec on a search that came up empty. After the upgrade all searches required the wait. So that was a downgrade of the search function.
I just had that happen to me. I’m not the least bit bothered though. I have those 246 seconds to spare. Just so long as it doesn’t keep happening.
Or to put it another way: Just so long as what I wanted to find and respond to gets found and responded to before my patience runs out. And I have a lot of patience.
Well, if you do type Sorny, you’ll probably get a thread about that Simpsons episode where they go to the outlet mall and find Magnetbox and Sorny electronic equipment.
You know, the one where Marge finds the Gucci pantsuit thingy and they all get invited to the country club.
Damn! Typing this post only consumed 22 seconds.
OK, back.
Yeah, I was lamenting that because of an unspecified database error, you’re still “charged” for a search. I can actually understand being charged for a search that returns no results, aggravating as it may be. Fuckups on the house side should be on the house, though.
And of course you try to hit Refresh and you get the “sorry chump, you gotta wait 300 seconds” message.
Ah well it’s not like there’s anything really worth searching for here anyway.
I’ve noticed “” marks, or any punctuation can cause database errors. So can Boolean operators.