The /10 syntax makes sense to programmers but I think users are going to forget it pretty quickly. Same with "OR" an "NEAR" being required to be all caps (I didn't know that). Ideally the UI an application exposes would show the user that OR and NEAR were interpreted as keywords and not tokens (of course that's up to individual application developers and not an issue for sqlite/fts).
Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, September 14, 2007 3:45 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Adding additional operators to FTS3 "Scott Hess" <[EMAIL PROTECTED]> wrote: > > One thing I'll think on in the background as a how-to-integrate > question is the balance between sophistication for query experts > versus the approachability for non-experts. For some systems, having > things like proximity queries complicates the query language to no > particular end, while in other systems proximity queries might be > essential. Insofar as more sophisticated query forms don't interfere > with simpler forms, they can just be ignored, but it would be nice if > they didn't crop up in warts like unexpected results for a search > 'stoplight near krispy kreme' where you no longer find documents where > stoplight is more than 10 terms away from krispy. We've discussed > having the ability to express both more ad-hoc and more stylized > queries, maybe this is something to think about along those lines. > The OR operator has to be all caps in order to be recognized as an operator and not the word "or". Presumably the NEAR operator would work the same way. That would minimize the chance of a collision with the word "near". We might also require the "/10" after the NEAR keyword or else it goes back to just being the token "near" and not an operator. -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
