Shopsmith Forums

Pardon the pun Admin, but this is bs.

JPG
I have a spell checker in my office package that also breaks up that word. Also others like skillsaw and such. Must be the version of the King's English preferred by the programmers. Have you tried Shopsmith Yet? Seems to want that one broken up also.
Bill

I deleted my comments.

More of the same.
I cannot seem to be able to get google to find things either!

Actually I be hoping Admin can 'fix'.

I'm glad you brought this up. The ability to construct more complicated searches using advance search is hindered by software that ignores words. Since we don't all use the best English all the time, I'd like to be able to search "bandsaw" or "band" + "saw" and I don't see why any words need be ignored.

I've made a note to check into it. I bumped the common words setting to 40% of the posts and it still rejected bandsaw. I know "bandsaw" isn't in 40% or more of the posts, I'm guessing a search index corruption. I'll pick a slow time and let it rebuild the index and see if that fixes it.

admin wrote:I've made a note to check into it. I bumped the common words setting to 40% of the posts and it still rejected bandsaw. I know "bandsaw" isn't in 40% or more of the posts, I'm guessing a search index corruption. I'll pick a slow time and let it rebuild the index and see if that fixes it.

When you rebuild the index, do you do this with the DB on the online server or do you export the DB to a 'local host' and then rebuild using that DB copy?

It seems like rebuilding the index on a 'local host' would be a lot faster. The DB is not small (181,072 posts) so the rebuild could take a couple days.

dusty wrote:

admin wrote:I've made a note to check into it. I bumped the common words setting to 40% of the posts and it still rejected bandsaw. I know "bandsaw" isn't in 40% or more of the posts, I'm guessing a search index corruption. I'll pick a slow time and let it rebuild the index and see if that fixes it.

When you rebuild the index, do you do this with the DB on the online server or do you export the DB to a 'local host' and then rebuild using that DB copy?

It seems like rebuilding the index on a 'local host' would be a lot faster. The DB is not small (181,072 posts) so the rebuild could take a couple days.

Not as bad as you'd imagine. It rebuilds the index at a rate a little over 40 post per second. 181072/40 = 4527 seconds, 4527/60 = 75 minutes.

Re-index is completed. The problem appears solved for now.

admin wrote:Re-index is completed. The problem appears solved for now.

THANK YOU!!!!!!

BTW 200 is NOT 'huge'