9934 2010-06-16 00:11:28 +0000 [FT] Need static error for unsupported FTMatchOptions combinations 2010-12-29 17:02:25 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Candidate Recommendation All All CLOSED WORKSFORME P2 normal --- 1 paul jim.melton holstege public-qt-comments oldest_to_newest 36205 0 paul 2010-06-16 00:11:28 +0000 If an implementation does not support a particular combination of FTMatchOptions in a single query, it should raise a static error. However, the specification does not currently provide such an error. For example, given a query like: $x contains text ".*volv.*" using stemming using wildcards it's not clear what that means, what a correct answer would be, or even how to implement it. 36639 1 holstege 2010-07-06 18:20:18 +0000 The WG discussed this bug at the 2010-07-06 telcon. We believe that the current specification gives implementations sufficient latitude to handle such cases without error and we do not wish to give implementations license to throw an error in such as case, as it imposes an undue burden on users in constructing error-free queries. It is quite likely, for example, that stemming could be a global option, which would create the same conflict. Stemming, tokenization, and matching are already all implementation dependent, so the implementation can choose to define the effect in such cases in a suitable manner. While it is unlikely that stemming will perform any meaningful operation on a wildcarded token (just as it will not for a numeric token, for example) in the query, stemming can still be applied meaningfully to the document content and it is possible that the wildcarded token could be matched in a stem-aware fashion. In summary, we are closing this bug with no further action. If you are satisfied with this resolution, please close the bug.