How to Report Bugs or Problems the syntax you are using. If you are using the current version and the manual doesn’t cover the syntax that you are using, MySQL Server doesn’t support your statement. If the manual covers the syntax you are using, but you have an older version of MySQL Server, you should check the MySQL change history to see when the syntax was implemented. In this case, you have the option of upgrading to a newer version of MySQL Server. If you cannot find an answer in the manual, the bugs database, or the mailing list archives, check with your local MySQL expert. If you still cannot find an answer to your question, please use the following guidelines for reporting the bug. •For solutions to some common problems, see Section B.3, “Problems and Common Errors” . •Search the bugs database at http://bugs.mysql.com/ to see whether the bug has been reported and fixed. •You can also use http://www.mysql.com/search/ to search all the Web pages (including the manual) that are located at the MySQL website. The normal way to report bugs is to visit http://bugs.mysql.com/, which is the address for our bugs database. This database is public and can be browsed and searched by anyone. If you log in to the system, you can enter new reports. Bugs posted in the bugs database at http://bugs.mysql.com/ that are corrected for a given release are noted in the release notes. If you find a security bug in MySQL Server, please let us know immediately by sending an email message to  <secalert_us@oracle.com> . Exception: Support customers should report all problems, including security bugs, to Oracle Support at http://support.oracle.com/. To discuss problems with other users, you can use the MySQL Community Slack. Writing a good bug report takes patience, but doing it right the first time saves time both for us and for yourself. A good bug report, containing a full test case for the bug, makes it very likely that we will fix the bug in the next release. This section helps you write your report correctly so that you do not waste your time doing things that may not help us much or at all. Please read this section carefully and make sure that all the information described here is included in your report. Preferably, you should test the problem using the latest production or development version of MySQL Server before posting. Anyone should be able to repeat the bug by just using  mysql test < script_file  on your test case or by running the shell or Perl script that you include in the bug report. Any bug that we are able to repeat has a high chance of being fixed in the next MySQL release. It is most helpful when a good description of the problem is included in the bug report. That is, give a good example of everything you did that led to the problem and describe, in exact detail, the problem itself. The best reports are those that include a full example showing how to reproduce the bug or problem. See Section 5.9, “Debugging MySQL” . Remember that it is possible for us to respond to a report containing too much information, but not to one containing too little. People often omit facts because they think they know the cause of a problem and assume that some details do not matter. A good principle to follow is that if you are in doubt about stating something, state it. It is faster and less troublesome to write a couple more lines in your report than to wait longer for the answer if we must ask you to provide information that was missing from the initial report. The most common errors made in bug reports are (a) not including the version number of the MySQL distribution that you use, and (b) not fully describing the platform on which the MySQL server is installed 72