Bug #15945 | Online manual search fails to find certain reserved words | ||
---|---|---|---|
Submitted: | 22 Dec 2005 23:04 | Modified: | 24 Nov 2009 16:44 |
Reporter: | Dave Caroline | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | all | OS: | Any (not applicable) |
Assigned to: | Stefan Hinz | CPU Architecture: | Any |
[22 Dec 2005 23:04]
Dave Caroline
[2 Jan 2006 13:51]
Stefan Hinz
There's nothing we can do about this on the documentation team's side. What we need is a better crawler (we're currently using Mnogo), and that's something only our webmasters can set up. They're aware of issues like the ones described in this bug report, but since changing the crawler isn't a trivial task this won't be done anytime soon. Sorry.
[6 Nov 2009 17:10]
Valeriy Kravchuk
Please, check how it works for, say, WHERE searching now in 5.1 manual for example (see http://search.mysql.com/search?site=refman-51&q=where&lr=lang_en). Are you satisfied with the results?
[6 Nov 2009 17:28]
Dave Caroline
yes your example of where is better but try http://search.mysql.com/search?q=in&site=refman-51&btnG=Search join freenode #mysql-dev or #mysql and type <archivist> !noo in <the_wench> see http://dev.mysql.com/doc/refman/5.1/en/comparison-operators.html#function_in this is done by trawling the doc source xml, it can be done
[24 Nov 2009 16:44]
Stefan Hinz
According to the comments, the issue with not being able to find WHERE is resolved. Regarding IN(), this function is documented as "expr IN (value,...)" -- without "expr" IN() doesn't make much sense. Consequently, IN() can be found when looking for the context; see: http://search.mysql.com/search?q=expr+in+IN&site=refman-51&btnG=Search&sort=date%3AD%3AL%3.... Regarding AS, FOR, and IS, there's no reasonable reason for looking up these words -- they're neither functions nor operators, and make sense only in context such as SELECT ... FOR UPDATE.