When I do these three searches, I get completely different results (e.g., some threads appear in one and not the others.) Anyone else notice this weirdness? I can provide actual examples if it will be useful.
[ul]
[li]Advanced Search by “exact” username.[/li][li]Advanced Search by “inexact” username, which should be a superset of search by exact username, but isn’t.[/li][li]Generic “Search” offered under the Search tab on the main screen menubar.[/li][/ul]
Baffling, especially threads that show up in search by exact username, but don’t show up in search by inexact username.
Search is the most server-intensive thing we have going on and it really takes a toll on system resources.
Sometimes it doesn’t deliver reliably, most likely because at times of stress, the server throws up its little hands and resets itself. (So to speak.) Some tasks get dropped and others are done incompletely.
Please be judicious in your use of search and don’t have too high of an expectation, especially at peak times. This ain’t Google.
Then perhaps Ed’s post on “what you get when you subscribe” should be modified to say “You can use the search function, but we’d rather you didn’t use it too often, and we can’t guarantee that you’ll get consistant results or, for that matter, very good results at all” from “Ability to search the massive SDMB message database”.
I hope you don’t mind the hijack, neuroman, but what is the status on the massive “thread re-indexing” that was going on after the software upgrade? I still get big holes in the search results, to the tune of several months or a year, when searching on what I thought were common keywords. Are there gaps in the index still, or is that the server just giving up?
I happen to have another question myself (which has probably been asked somewhere else already, but I’d have to tax server resources to find that out ).
The default “search” used to be limited to the last 24 hours - the idea being that the most common search for users is a one day vandity search. Seems like it would be a good idea to reinstitute the 24 hr. default instead of having “any time ever” be the default. Any plans for this?
It might; it might not. It depends on how intelligently the SQL indexing function was structured. If there is a continuously-maintained index file that excludes all but certain records, yes. Otherwise, all records would have to be searched anyway, no matter how small the numbers are that pass thru the filter.
I guess someone who knows how the vB code was coded and how it interfaces with SQL is needed here. I haven’t gone that deep into their structure.
The search function is definitely not working properly. I just did a search for threads with a certain word in the title, and I got back every thread that included the word anywhere in the thread. I hit the back button and checked, so I know I didn’t screw up. And yesterday I searched for an old post of mine using my username and a keyword and it didn’t turn up, though I eventually found it. I never noticed these kinds of malfunctions before.
I was looking for a thread from a while back. I used a number of different key words, none of which brought it up. I then searched on my own name. That did bring it up, but it took a lot of digging.
If you’re interested, here’s the thread:
Some of the keywords I entered were “estimate,” “stealing,” and “bill.”
So, yes, the search engine is definitely not reliable when it comes to keywords. Searching by user name does seem to work a little better when that info is available.
Likewise. I generally have to search for a particular thread/post several different ways (thread title vs. all posts, different keywords, different usernames of people I remember posting in the thread) before I find it. I frequently just give up, but that has got to be taxing the board more than necessary.
Well, if our overworked, underpaid (unpaid?), under-appreciated technical staff can figure out what’s a transpirin’ with the search engine and fix it, I know we’d have at least a few happy dopers.
I started to google vbulletin search engine stuff but don’t have time to wade through it right now…
).