I know I'm new here, so my opinion won't count much, but I too feel that non-wildcard matching should be the default option. Most people, nowdays, have a general idea of globbing (if not RE), so they'll know what a * does. Plus, it would follow a similar syntax to the bourne shell. Consistency is important!<br>
<br>- Vishesh Handa<br><br><div class="gmail_quote">On Wed, Mar 10, 2010 at 9:07 PM, todd rme <span dir="ltr"><<a href="mailto:toddrme2178@gmail.com">toddrme2178@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Wed, Mar 10, 2010 at 10:11 AM, Sebastian Trueg <<a href="mailto:trueg@kde.org">trueg@kde.org</a>> wrote:<br>
> Currently the Nepomuk query API will add a wildcard '*' to each full<br>
> text search term so terms like "Nepo" will also match "Nepomuk".<br>
> Recently some concern has been raised[1] about this practice and I tend<br>
> to agree with it.<br>
> Basically the competing idea is to not add a wildcard automatically but<br>
> let the user specify it like so:<br>
><br>
> "nepo*"<br>
><br>
> The advantage is that 1. we would support both wildcard matching and<br>
> non-wildcard matching and 2. simple full-text queries would be speed up<br>
> a little bit. The disadvantage is that it would be a behavioral change<br>
> in the API (the old behavior is not documented though).<br>
><br>
> So I need some opinions here.<br>
<br>
</div>I think it is essential to support non-wildcard matching. I am not<br>
clear on which should be the default, but in the absence of suggestion<br>
of a good way to force non-wildcard matching I think that this is<br>
really the only option.<br>
<font color="#888888"><br>
-Todd<br>
</font><div><div></div><div class="h5"><br>
>> Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to unsubscribe <<<br>
</div></div></blockquote></div><br>