Hi Dave ! Thank you for your answer, i've totally understood the matter and i must say that's quite annoying... I guess that you won't satisfy everyone with removing this feature, because it really depends on the application you wanna run.. Someone running something like a wiki would like to get the same results with e-mail and email, that's correct and it's of course a good feature, but in my case, i really don't want my query "name:package-dev" to send back 'package-foobar-dev' etc... that's a really big problem for me.
Actually, i think using different operators calling different parsing methods could be a *correct* solution, like "type:e-mail" would match email and 'e mail' and "type=e-mail" would only match "e-mail" (in regexp: /^e-mail.*/). The '=' operator is quite self explanatory for exact pattern matching, so it could be easy to understand... It could be a way to keep the flexibility of the current search matching method, and to include a more strict pattern method for those who needs that.. Anyway, Thank you for the solution ! Cheers, Jeremie 'ahFeel' BORDIER -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
