Search is a big issue.

The reason is, if ita will forgive me, that there's a built-in way to make databases easily searchable.

But our using that built-in method seems like it was one of the reasons behind the big crash of February.

But that built-in way is the most efficient way. Any other way would almost certainly create just as many problems.

What do you mean, exactly, John? Are you referring to full text? It's less load than LIKE. The key is making the search more efficient -- not presenting all the results on one page, yadda, yadda.

And I'll get to it.

What do you mean, exactly, John? Are you referring to full text?

Yes, sorry if I mis-represented the situation -- I thought you'd said earlier that fulltext searches were part of the thing that crashed the board before.

Well, it was fulltext searches, but any multiple searches that returned 1100 hits a shot from going through post contents would have crashed the server -- fulltext just not as soon as LIKE.

Just tried to Threadsuck PPO, received a fatal error with the text that's generated by this board, not my browser or computer. Kudos to whomever wrote that, by the way, but I'd really like a way to read the pretty alien-boy/rich-boy slash offline.

not meaning to be nagging unappreciative board user.

but I'd really like a way to read the pretty alien-boy/rich-boy slash offline.

You know, maybe that error page should automatically feed you some of this to ease the sting. What?

What were your settings, connie? Start and end posts, plus were you having them marked as read?

not meaning to be nagging unappreciative board user.

Too late, busted, going in your permanent file.

Start and end posts both set to blank, not mark as read, I have gone to the end of the thread (but I skipped a great deal, so who knows what pretty things I may have missed?) so there are no posts in the thread that are unread.

pulls out DavidS's file on connie

begins to write "nagging unappreciative board user" in comment box

just writes NABU instead.