Bug #13974 | Online documentation searches not available or dont work | ||
---|---|---|---|
Submitted: | 12 Oct 2005 19:15 | Modified: | 14 Nov 2005 17:29 |
Reporter: | Jon Koerber | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S2 (Serious) |
Version: | Current | OS: | Linux (Linux, Windows, Mac OSX) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[12 Oct 2005 19:15]
Jon Koerber
[13 Oct 2005 6:56]
Valeriy Kravchuk
Thank you for a documentation problem report. "I can no longer perform searches within the MySQL 4.1 online manual. There isn't even an option to perform a search??? " Verified. There is no Search box in 4.1 documentation, but there is one in 5.0. "Additionally if I select to use the 5.0 or 5.1 manual, my searches all produce a "FILE NOT FOUND" error. For example just type the word "REPLACE" into the search box to find the correct syntax for the MySQL REPLACE command." Yes, it displays the additional search box. If you specify REPLACE in it and ask to search in the Manual, it will give you proper links. But for 5.0. "I sincerely hope this problem will be corrected soon and that the high quality of the MySQL product team will continue to show." I hope so too. "But when I clicked on the "REPLACE syntax" link which was: (http://dev.mysql.com/doc/mysql/en/REPLACE.html) it redirects me to (http://dev.mysql.com/doc/refman/5.0/en/en/REPLACE.html)." It is a link to http://dev.mysql.com/doc/refman/5.0/en/replace.html now, and it gives you just that page.
[14 Oct 2005 17:28]
MySQL Verification Team
Search for replace
Attachment: bug13974.PNG (image/x-png, text), 76.05 KiB.
[14 Oct 2005 17:29]
MySQL Verification Team
I was able to search and found results for the key replace. I attached a picture showing that. Could you please try again.
[15 Nov 2005 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".