Thanks,
jugulear, for the detailed description. Why I asked for it: I'm getting description of bugs everyday from colleagues and customers. And I know how hard it is to find potential bugs. Not seldom its not a bug, but the user who didn't understand something or simply expected something different.
So it means the search works like this at the moment:
- If you enter 'NHDT129' (without the single quote, of course) it really searches for this token. Only 'NHDT129' will be found. Combinations like 'NHDT 129', '129 NHDT' or 'NHDT-129' in the title or post won't be found.
- If you enter 'NHDT-129' it will search for 'NHDT' AND '129'. All the combinations - 'NHDT129', 'NHDT 129', '129 NHDT', 'NHDT-129' will be found.
- If you enter 'NHDT 129' or '129 NHDT' it also means 'NHDT' AND '129'. In this case also all combinations will be found.
- If you enter the term in double quotes exactly this token will be found.
- '"NHDT129"' will only find 'NHDT129', but none of the other combinations.
- '"NHDT-129"' will only find 'NHDT-129', but none of the other combinations.
- '"NHDT 129"' will only find 'NHDT 129', but none of the other combinations.
- '"129 NHDT"' will only find '129 NHDT', but none of the other combinations.
I have to say that this is what I would have expected. But maybe it's from a developer's point of view. As we use some normal forum software the search isn't aware of the meaning of movie codes and how they work. So it wouldn't understand that 'NHDT129' could also means 'NHDT-129' or 'NHDT 129'. It's just a dump normal full-text search.
By the way: Of course the search may also search in the tags of the threads.