首先在 https://dev.mysql.com/doc/。我们通过经常更新新发现问题的解决方案来努力使手册保持最新状态。此外，手册附带的发行说明可能特别有用，因为较新的版本很可能包含您问题的解决方案。发行说明可在手册中给出的位置找到。Start by searching the MySQL online manual at https://dev.mysql.com/doc/. We try to keep the manual up to date by updating it frequently with solutions to newly found problems. In addition, the release notes accompanying the manual can be particularly useful since it is quite possible that a newer version contains a solution to your problem. The release notes are available at the location just given for the manual.

如果您收到 SQL 语句的解析错误，请仔细检查您的语法。如果您找不到问题，则很可能您当前版本的 MySQL Server 不支持您正在使用的语法。如果您使用的是当前版本，并且手册未涵盖您正在使用的语法，则 MySQL Server 不支持您的语句。If you get a parse error for an SQL statement, please check your syntax closely. If you cannot find something wrong with it, it is extremely likely that your current version of MySQL Server doesn't support 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.

如果手册涵盖了您正在使用的语法，但您拥有较旧版本的 MySQL Server，则应检查 MySQL 更改历史记录以了解该语法何时实施。在这种情况下，您可以选择升级到较新版本的 MySQL Server。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.

有关一些常见问题的解决方案，请参阅第 B.3 节“问题和常见错误”。For solutions to some common problems, see Section B.3, “Problems and Common Errors”.

在 http://bugs.mysql.com/ 查看错误是否已报告并修复。Search the bugs database at http://bugs.mysql.com/ to see whether the bug has been reported and fixed.

您还可以使用http://www.mysql.com/search/ 搜索位于 MySQL 网站的所有网页（包括手册）。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.

您正在使用的 MySQL 发行版的版本号（例如，MySQL 5.7.10）。您可以通过执行mysqladmin version来了解您正在运行的版本。 mysqladmin 程序可以在 MySQL 安装目录下的 bin 目录中找到。The version number of the MySQL distribution you are using (for example, MySQL 5.7.10). You can find out which version you are running by executing mysqladmin version. The mysqladmin program can be found in the bin directory under your MySQL installation directory.

您遇到问题的计算机的制造商和型号。The manufacturer and model of the machine on which you experience the problem.

操作系统名称和版本。如果您使用 Windows，通常可以通过双击“我的电脑”图标并下拉“帮助/关于 Windows” 菜单来获取名称和版本号。对于大多数类 Unix 操作系统，您可以通过执行命令 uname -a 来获取此信息。The operating system name and version. If you work with Windows, you can usually get the name and version number by double-clicking your My Computer icon and pulling down the “Help/About Windows” menu. For most Unix-like operating systems, you can get this information by executing the command uname -a.

有时内存量（实际和虚拟）是相关的。如果有疑问，请包含这些值。Sometimes the amount of memory (real and virtual) is relevant. If in doubt, include these values.

MySQL 安装中的 docs/INFO_BIN 文件的内容。此文件包含有关如何配置和编译 MySQL 的信息。The contents of the docs/INFO_BIN file from your MySQL installation. This file contains information about how MySQL was configured and compiled.

如果您使用的是 MySQL 软件的源发行版，请包含您使用的编译器的名称和版本号。如果您有二进制发行版，请包含发行版名称。If you are using a source distribution of the MySQL software, include the name and version number of the compiler that you used. If you have a binary distribution, include the distribution name.

如果在编译过程中出现问题，请包含确切的错误消息以及发生错误的文件中违规代码周围的几行上下文。If the problem occurs during compilation, include the exact error messages and also a few lines of context around the offending code in the file where the error occurs.

如果 mysqld 死机，您还应该报告该语句这导致 mysqld 意外退出。通常，您可以通过在启用查询日志记录的情况下运行 mysqld 来获取此信息，然后在 mysqld 退出。请参阅第 7.9 节“调试 MySQL”。If mysqld died, you should also report the statement that caused mysqld to unexpectedly exit. You can usually get this information by running mysqld with query logging enabled, and then looking in the log after mysqld exits. See Section 7.9, “Debugging MySQL”.

如果表与问题相关，请在错误报告中包含SHOW CREATE TABLE db_name.tbl_name语句的输出。这是获取数据库中任何表定义的非常简单的方法。这些信息帮助我们创建与您所经历的情况相匹配的情景。If a database table is related to the problem, include the output from the SHOW CREATE TABLE db_name.tbl_name statement in the bug report. This is a very easy way to get the definition of any table in a database. The information helps us create a situation matching the one that you have experienced.

问题发生时有效的 SQL 模式可能非常重要，因此请报告 sql_mode 系统变量的值。对于存储过程、存储函数和触发器对象，相关的 sql_mode 值是创建对象时有效的值。对于存储过程或函数，SHOW CREATE PROCEDURE 或 SHOW CREATE FUNCTION语句显示相关的 SQL 模式，或者您可以查询INFORMATION_SCHEMA获取信息：The SQL mode in effect when the problem occurred can be significant, so please report the value of the sql_mode system variable. For stored procedure, stored function, and trigger objects, the relevant sql_mode value is the one in effect when the object was created. For a stored procedure or function, the SHOW CREATE PROCEDURE or SHOW CREATE FUNCTION statement shows the relevant SQL mode, or you can query INFORMATION_SCHEMA for the information:

SELECT ROUTINE_SCHEMA, ROUTINE_NAME, SQL_MODE
FROM INFORMATION_SCHEMA.ROUTINES;

对于触发器，您可以使用此语句：For triggers, you can use this statement:

SELECT EVENT_OBJECT_SCHEMA, EVENT_OBJECT_TABLE, TRIGGER_NAME, SQL_MODE
FROM INFORMATION_SCHEMA.TRIGGERS;

对于 SELECT 语句的性能相关错误或问题，您应始终包含 EXPLAIN SELECT ... 的输出，并且至少包含 SELECT 语句产生。您还应该为涉及的每个表包含 SHOW CREATE TABLE tbl_name 的输出。您提供的有关您的情况的信息越多，别人就越有可能为您提供帮助。For performance-related bugs or problems with SELECT statements, you should always include the output of EXPLAIN SELECT ..., and at least the number of rows that the SELECT statement produces. You should also include the output from SHOW CREATE TABLE tbl_name for each table that is involved. The more information you provide about your situation, the more likely it is that someone can help you.

以下是一个非常好的错误报告示例。这些语句使用 mysql 命令行工具运行。请注意对语句使用 \G 语句终止符，否则会提供非常长且难以阅读的输出行。The following is an example of a very good bug report. The statements are run using the mysql command-line tool. Note the use of the \G statement terminator for statements that would otherwise provide very long output lines that are difficult to read.

mysql> SHOW VARIABLES;
mysql> SHOW COLUMNS FROM ...\G
       <output from SHOW COLUMNS>
mysql> EXPLAIN SELECT ...\G
       <output from EXPLAIN>
mysql> FLUSH STATUS;
mysql> SELECT ...;
       <A short version of the output from SELECT,
       including the time taken to run the query>
mysql> SHOW STATUS;
       <output from SHOW STATUS>

如果在运行 mysqld 时出现错误或问题，请尝试提供重现异常的输入脚本。该脚本应包含任何必要的源文件。脚本越能准确地再现您的情况就越好。如果您可以制作可重现的测试用例，则应将其上传以附加到错误报告中。If a bug or problem occurs while running mysqld, try to provide an input script that reproduces the anomaly. This script should include any necessary source files. The more closely the script can reproduce your situation, the better. If you can make a reproducible test case, you should upload it to be attached to the bug report.

如果您无法提供脚本，则至少应在报告中包含 mysqladmin 变量扩展状态进程列表 的输出，以提供有关系统运行情况的一些信息If you cannot provide a script, you should at least include the output from mysqladmin variables extended-status processlist in your report to provide some information on how your system is performing.

如果您无法生成只有几行的测试用例，或者测试表太大而无法包含在错误报告中（超过 10 行），您应该使用 mysqldump 转储表并创建一个 README 文件描述您的问题。使用 tar 和 gzip 或 zip 创建文件的压缩存档。当您在 http://bugs.mysql.com/ 为我们的错误数据库发起错误报告后，请单击错误报告中的“文件”选项卡，获取有关将存档上传到错误数据库的说明。If you cannot produce a test case with only a few rows, or if the test table is too big to be included in the bug report (more than 10 rows), you should dump your tables using mysqldump and create a README file that describes your problem. Create a compressed archive of your files using tar and gzip or zip. After you initiate a bug report for our bugs database at http://bugs.mysql.com/, click the Files tab in the bug report for instructions on uploading the archive to the bugs database.

如果您认为 MySQL 服务器从语句中产生了奇怪的结果，请不仅包括结果，还包括您对结果应该是什么的看法，以及描述您的错误基础的解释。意见。If you believe that the MySQL server produces a strange result from a statement, include not only the result, but also your opinion of what the result should be, and an explanation describing the basis for your opinion.

当你提供问题的例子时，最好使用你实际情况中存在的表名、变量名等，而不是想出新的名称。该问题可能与表或变量的名称有关。这些情况也许很少见，但安全总比后悔好。毕竟，您提供一个符合您实际情况的示例应该会更容易，而且对我们来说绝对更好。如果您不希望错误报告中的其他人看到您的数据，您可以使用“文件”选项卡上传该数据，如前所述。如果信息确实是绝密的，并且您甚至不想向我们展示，请继续使用其他名称提供示例，但请将此视为最后的选择。When you provide an example of the problem, it is better to use the table names, variable names, and so forth that exist in your actual situation than to come up with new names. The problem could be related to the name of a table or variable. These cases are rare, perhaps, but it is better to be safe than sorry. After all, it should be easier for you to provide an example that uses your actual situation, and it is by all means better for us. If you have data that you do not want to be visible to others in the bug report, you can upload it using the Files tab as previously described. If the information is really top secret and you do not want to show it even to us, go ahead and provide an example using other names, but please regard this as the last choice.

如果可能，请包括为相关程序提供的所有选项。例如，指示启动 mysqld 服务器时使用的选项，以及用于运行任何 MySQL 客户端程序的选项。 mysqld 和 mysql 等程序的选项，以及configure 脚本通常是解决问题的关键并且非常相关。将它们包括在内绝不是一个坏主意。如果您的问题涉及用 Perl 或 PHP 等语言编写的程序，请包含语言处理器的版本号以及程序使用的任何模块的版本。例如，如果您有一个使用 DBI 和 DBD::mysql 模块的 Perl 脚本，请包含 Perl、DBI 和 DBD::mysql 的版本号。Include all the options given to the relevant programs, if possible. For example, indicate the options that you use when you start the mysqld server, as well as the options that you use to run any MySQL client programs. The options to programs such as mysqld and mysql, and to the configure script, are often key to resolving problems and are very relevant. It is never a bad idea to include them. If your problem involves a program written in a language such as Perl or PHP, please include the language processor's version number, as well as the version for any modules that the program uses. For example, if you have a Perl script that uses the DBI and DBD::mysql modules, include the version numbers for Perl, DBI, and DBD::mysql.

如果您的问题与权限系统相关，请包含 mysqladmin reload，以及尝试连接时收到的所有错误消息。当您测试权限时，您应该执行mysqladmin 重新加载版本并尝试连接给您带来麻烦的程序。If your question is related to the privilege system, please include the output of mysqladmin reload, and all the error messages you get when trying to connect. When you test your privileges, you should execute mysqladmin reload version and try to connect with the program that gives you trouble.

如果您有针对错误的补丁，请务必将其包含在内。但是，如果您不提供一些必要的信息（例如显示补丁修复的错误的测试用例），请不要假设该补丁就是我们所需要的，或者我们可以使用它。我们可能会发现您的补丁有问题，或者我们可能根本不理解它。如果是这样，我们就不能使用它。If you have a patch for a bug, do include it. But do not assume that the patch is all we need, or that we can use it, if you do not provide some necessary information such as test cases showing the bug that your patch fixes. We might find problems with your patch or we might not understand it at all. If so, we cannot use it.

如果我们无法验证补丁的确切用途，我们就不会使用它。测试用例在这里对我们有帮助。表明该补丁可以处理所有可能发生的情况。如果我们发现补丁不起作用的临界情况（即使是罕见的情况），它可能毫无用处。If we cannot verify the exact purpose of the patch, we will not use it. Test cases help us here. Show that the patch handles all the situations that may occur. If we find a borderline case (even a rare one) where the patch will not work, it may be useless.

对错误是什么、为什么会发生或者它依赖什么的猜测通常是错误的。如果不首先使用调试器来确定错误的真正原因，即使是 MySQL 团队也无法猜测此类事情。Guesses about what the bug is, why it occurs, or what it depends on are usually wrong. Even the MySQL team cannot guess such things without first using a debugger to determine the real cause of a bug.

在错误报告中表明您已检查了参考手册和邮件存档，以便其他人知道您已尝试自行解决问题。Indicate in your bug report that you have checked the reference manual and mail archive so that others know you have tried to solve the problem yourself.

如果您的数据出现损坏或在访问特定表时遇到错误，请首先使用CHECK TABLE检查您的表。如果该语句报告任何错误：If your data appears corrupt or you get errors when you access a particular table, first check your tables with CHECK TABLE. If that statement reports any errors:

如果您运行的是 Windows，请验证 lower_case_table_names 使用 SHOW VARIABLES LIKE 'lower_case_table_names' 语句。此变量影响服务器处理数据库和表名称的字母大小写的方式。它对给定值的影响应如第 11.2.3 节“标识符区分大小写” 中所述。If you are running Windows, please verify the value of lower_case_table_names using the SHOW VARIABLES LIKE 'lower_case_table_names' statement. This variable affects how the server handles lettercase of database and table names. Its effect for a given value should be as described in Section 11.2.3, “Identifier Case Sensitivity”.

如果您经常遇到损坏的表，您应该尝试找出发生这种情况的时间和原因。在这种情况下，MySQL 数据目录中的错误日志可能包含有关所发生情况的一些信息。 （这是名称中带有 .err 后缀的文件。）请参阅第 7.4.2 节“错误日志”。请将此文件中的任何相关信息包含在您的错误报告中。通常，如果在更新过程中没有任何东西杀死表，mysqld 应该永远不会损坏表。如果您能找到 mysqld 死机的原因，我们就可以更轻松地为您提供问题的解决方案。请参阅第 B.3.1 节“如何确定导致问题的原因”。If you often get corrupted tables, you should try to find out when and why this happens. In this case, the error log in the MySQL data directory may contain some information about what happened. (This is the file with the .err suffix in the name.) See Section 7.4.2, “The Error Log”. Please include any relevant information from this file in your bug report. Normally mysqld should never corrupt a table if nothing killed it in the middle of an update. If you can find the cause of mysqld dying, it is much easier for us to provide you with a fix for the problem. See Section B.3.1, “How to Determine What Is Causing a Problem”.

如果可能，请下载并安装最新版本的 MySQL Server 并检查它是否可以解决您的问题。所有版本的 MySQL 软件都经过彻底测试，应该可以正常运行。我们相信让一切尽可能向后兼容，并且您应该能够毫无困难地切换 MySQL 版本。请参阅第 2.1.2 节“要安装哪个 MySQL 版本和发行版”。If possible, download and install the most recent version of MySQL Server and check whether it solves your problem. All versions of the MySQL software are thoroughly tested and should work without problems. We believe in making everything as backward-compatible as possible, and you should be able to switch MySQL versions without difficulty. See Section 2.1.2, “Which MySQL Version and Distribution to Install”.