3920 2006-10-31 23:42:21 +0000 [FT] Section 3.1.8 Examples 2007-04-20 15:42:25 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Working drafts PC Windows XP CLOSED FIXED P2 normal --- 1 mrys jim.melton public-qt-comments oldest_to_newest 12713 0 mrys 2006-10-31 23:42:21 +0000 /book ftcontains ("information" && "retrieval") not in ("information" && "retrieval" distance at least 11 words) why use the mild not in the example. /book[. ftcontains "web site" && "usability" distance at most 1 words]/title Does distance start/end at beginning or end of a phrase? “A similar query for the p element” what p element? Show query. 13887 1 jim.melton 2007-02-02 18:00:11 +0000 Bug #3898 is related to parts of this bug (the question regarding the distance from a phrase to another token); the solution to #3898 will resolve that part of this bug. The Task Force agreed to fix the first example in section 3.3.7, FTDistance, to remove the first parenthesized expression and the keywords "not in" and to fix the text in the paragraph preceding the example, and to use search terms that actually appear in the sample data. The TF also agreed to fix the third example in that section by replacing "." with ".//p" and modifying the preceding paragraph to use concepts such as 'the token in the phrase "web site" that is nearest to the token "usability"...' 14304 2 pcase 2007-03-02 17:47:26 +0000 Fixed the first example in section 3.3.7, FTDistance, to remove the first parenthesized expression and the keywords "not in" and to fix the text in the paragraph preceding the example, and to use search terms that actually appear in the sample data. Bugzilla Bug #3920, [FT] Section 3.1.8 Examples Pat substituted this preceding text: The following expression returns false, because "completion" and "errors" are less than 11 tokens apart: and this example book ftcontains ("completion" && "errors" distance at least 11 words) I believe that Jochen fixed the third example. Michael, please review and close if appropriate. Pat 14815 3 jim.melton 2007-04-20 15:42:25 +0000 Because you participated in the TF when this bug was resolved, we presume that your concerns are addressed appropriately. We are therefore marking this bug as CLOSED.