Your are viewing a read-only archive of the old DiS boards. Please hit the Community button above to engage with the DiS !
Is there some hidden secret I have to uncover before any query delivers a satisfactory result?
you get these really long articles telling you about bands you cant remember who they are, then get frustrated and give up.
it was okish before but then matt (i think) said he was making ot even better and now its just completely unusable!
You gotta use its operators, especially a + on keywords which must appear, and quotes around any exact phrase you're searching for:
Sucks, I know. That's why we have google.
if you put quotes on a two word phrase, often the first page of results wont even have that two word phrase on it!
but yeah, i know shit all about how computers do their stuff
that too would be a MySQL bug.
also i didnt mean that horribly, just thought it was funny that it was supposed to be improved but instead went mental
I'm not actually bothered :)
I just don't have much time to spend on it.
To be fair I don't think it actually got worse. All I did was turn on MySQL's boolean mode search features, which let you search more accurately if you know how.
Gotta know how though.
That's great. Could you turn it off again for about... half an hour? Thanks.
as this would leave the standard keyword search working the same, but stop people from being able to do the more advanced searches.
I type a couple of words in, and I get about 5 pages worth of shit articles from years ago.
you can search an exact thread title with username and still get nothing at all.
for an exact phrase search.
and the poster's username isn't currently indexed as part of the text
but i assume it's single quotes?
but the docs linked above have the details
i do SQL stuff half the week, so i dont want to spend my spare time on it too! ;)
(DiS is not my day job)
MySQL fulltext search is renowned for being a bit poo, but it's by far the easiest thing to implement on a website which uses mysql for the database.
The next best thing would be Lucene, but that would involve a lot of work to integrate and could eat quite a lot of disk and CPU too
No pain, no gain, brah.
Didn't think so :)
i wouldnt change anything without it being an official job, where you're getting paid for it.
i'm sure sean can prioritise changes to the board search.
to be fair I do get a bit, but big search improvements aren't in the the scope of it.
It just doesn't pay for a small company to invest a ton of time in trying to compete with google. And so you have something basic which will find keywords for you, and are free to use google if you want the damn thing to be psychic :)
i was trying to work out which classic dr who to start watching earlier, and all i got was massive review style posts. I hate having to take control of my own life!
i'll tell you!
However, using this formula in google works to a certain extent:
site: www.drownedinsound + funkargo + mature cheddar
site: www.drownedinsound + sarkyfox + "big business"
It does take a couple of days to pick it up - threads from today don't seem to work.
i've not seen any of them for over 10 years. Just been watching the first 4 tom baker ones. Who would you recommend?
tom baker wise, it's all ace from ark in space through to talons of weng chiang.
particularly genesis of the daleks and deadly assassin.
generally i think the very last season of the old series is the most interesting, with curse of fenric being pretty fantastic.
i think i'll get back on it with the ark and see how it goes.
the website will not grind to a halt as everyone tries to search..
You seem to get the phone book for every query. It would be nice if they appeared chronologically as most people will have some idea of the time frame what they are after was in - reviews / threads etc
beat me to it.
which makes it difficult to see what's going on.
can you make it ORDER BY date? which way doesnt really matter.
but then it wouldn't be ordering by relevance. Which would mean a different kind of suck.
i have no idea how many results it's actually returning sometimes, and it could be a similar nightmare.
that would be a MySQL bug.
Let me know the exact search you're using if you can actually replicate that...