Author: paul
Date: 2009-10-30 17:24:09 +0100 (Fri, 30 Oct 2009)
New Revision: 17398
Log:
r46005@frost: paul | 2009-10-30 11:22:08 -0500
Add a section describing the various sources of error information
Modified:
trunk/refman-4.1/errors-problems.xml
trunk/refman-5.0/errors-problems.xml
trunk/refman-5.1/errors-problems-core.xml
trunk/refman-5.4/errors-problems-core.xml
trunk/refman-5.5/errors-problems-core.xml
trunk/refman-6.0.sav/errors-problems.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:27523
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:46002
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
+ 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:27523
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:46005
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
Modified: trunk/refman-4.1/errors-problems.xml
===================================================================
--- trunk/refman-4.1/errors-problems.xml 2009-10-30 15:49:20 UTC (rev 17397)
+++ trunk/refman-4.1/errors-problems.xml 2009-10-30 16:24:09 UTC (rev 17398)
Changed blocks: 4, Lines Added: 88, Lines Deleted: 8; 3886 bytes
@@ -7,11 +7,6 @@
<title>Errors, Error Codes, and Common Problems</title>
- <remark role="todo">
- say something about SHOW WARNINGS, SHOW ERRORS, @warning_count,
- @error_count.
- </remark>
-
<para>
This appendix lists common problems and errors that may occur and
potential resolutions, in addition to listing the errors that may
@@ -33,6 +28,86 @@
</formalpara>
+ <section id="error-sources">
+
+ <title>Sources of Error Information</title>
+
+ <indexterm>
+ <primary>errors</primary>
+ <secondary>sources of information</secondary>
+ </indexterm>
+
+ <para>
+ There are several sources of error information in MySQL:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Each SQL statement executed results in an error code, an
+ SQLSTATE value, and an error message, as described in
+ <xref linkend="error-types"/>. These errors are returned from
+ the server side; see <xref linkend="error-messages-server"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Errors can occur on the client side, usually involving
+ problems communicating with the server; see
+ <xref linkend="error-messages-client"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ SQL statement warning and error information is available via
+ the <literal role="stmt">SHOW WARNINGS</literal> and
+ <literal role="stmt">SHOW ERRORS</literal> statements. The
+ <literal role="sysvar">warning_count</literal> and
+ <literal role="sysvar">error_count</literal> system variable
+ provide counts of the number of warnings and errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt">SHOW SLAVE STATUS</literal> statement
+ output includes information about replication errors occurring
+ on the slave side.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt" condition="show-engine">SHOW ENGINE
+ INNODB STATUS</literal> statement output includes information
+ about the most recent foreign key error if a
+ <literal role="stmt">CREATE TABLE</literal> statement for an
+ <literal role="se">InnoDB</literal> table fails.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <command>perror</command> program provides information
+ from the command line about error numbers. See
+ <xref linkend="perror"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Descriptions of server and client errors are provided later in
+ this Appendix. For information about errors related to
+ <literal role="se">InnoDB</literal>, see
+ <xref linkend="innodb-error-handling"/>.
+ </para>
+
+ </section>
+
<section id="error-types">
<title>Types of Error Values</title>
@@ -62,9 +137,13 @@
</itemizedlist>
<para>
+ A message string that provides a textual description of the error
+ is also available.
+ </para>
+
+ <para>
When an error occurs, you can access the MySQL error code, the
- SQLSTATE value, and a string containing an error message using C
- API functions:
+ SQLSTATE value, and the message string using C API functions:
</para>
<itemizedlist>
@@ -179,7 +258,8 @@
<listitem>
<para>
- A string that provides a textual description of the error.
+ A message string that provides a textual description of the
+ error.
</para>
</listitem>
Modified: trunk/refman-5.0/errors-problems.xml
===================================================================
--- trunk/refman-5.0/errors-problems.xml 2009-10-30 15:49:20 UTC (rev 17397)
+++ trunk/refman-5.0/errors-problems.xml 2009-10-30 16:24:09 UTC (rev 17398)
Changed blocks: 4, Lines Added: 88, Lines Deleted: 8; 3886 bytes
@@ -7,11 +7,6 @@
<title>Errors, Error Codes, and Common Problems</title>
- <remark role="todo">
- say something about SHOW WARNINGS, SHOW ERRORS, @warning_count,
- @error_count.
- </remark>
-
<para>
This appendix lists common problems and errors that may occur and
potential resolutions, in addition to listing the errors that may
@@ -33,6 +28,86 @@
</formalpara>
+ <section id="error-sources">
+
+ <title>Sources of Error Information</title>
+
+ <indexterm>
+ <primary>errors</primary>
+ <secondary>sources of information</secondary>
+ </indexterm>
+
+ <para>
+ There are several sources of error information in MySQL:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Each SQL statement executed results in an error code, an
+ SQLSTATE value, and an error message, as described in
+ <xref linkend="error-types"/>. These errors are returned from
+ the server side; see <xref linkend="error-messages-server"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Errors can occur on the client side, usually involving
+ problems communicating with the server; see
+ <xref linkend="error-messages-client"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ SQL statement warning and error information is available via
+ the <literal role="stmt">SHOW WARNINGS</literal> and
+ <literal role="stmt">SHOW ERRORS</literal> statements. The
+ <literal role="sysvar">warning_count</literal> and
+ <literal role="sysvar">error_count</literal> system variable
+ provide counts of the number of warnings and errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt">SHOW SLAVE STATUS</literal> statement
+ output includes information about replication errors occurring
+ on the slave side.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt" condition="show-engine">SHOW ENGINE
+ INNODB STATUS</literal> statement output includes information
+ about the most recent foreign key error if a
+ <literal role="stmt">CREATE TABLE</literal> statement for an
+ <literal role="se">InnoDB</literal> table fails.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <command>perror</command> program provides information
+ from the command line about error numbers. See
+ <xref linkend="perror"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Descriptions of server and client errors are provided later in
+ this Appendix. For information about errors related to
+ <literal role="se">InnoDB</literal>, see
+ <xref linkend="innodb-error-handling"/>.
+ </para>
+
+ </section>
+
<section id="error-types">
<title>Types of Error Values</title>
@@ -62,9 +137,13 @@
</itemizedlist>
<para>
+ A message string that provides a textual description of the error
+ is also available.
+ </para>
+
+ <para>
When an error occurs, you can access the MySQL error code, the
- SQLSTATE value, and a string containing an error message using C
- API functions:
+ SQLSTATE value, and the message string using C API functions:
</para>
<itemizedlist>
@@ -179,7 +258,8 @@
<listitem>
<para>
- A string that provides a textual description of the error.
+ A message string that provides a textual description of the
+ error.
</para>
</listitem>
Modified: trunk/refman-5.1/errors-problems-core.xml
===================================================================
--- trunk/refman-5.1/errors-problems-core.xml 2009-10-30 15:49:20 UTC (rev 17397)
+++ trunk/refman-5.1/errors-problems-core.xml 2009-10-30 16:24:09 UTC (rev 17398)
Changed blocks: 4, Lines Added: 88, Lines Deleted: 8; 3886 bytes
@@ -9,11 +9,6 @@
<remark role="dynamic-dependency-list"/>
- <remark role="todo">
- say something about SHOW WARNINGS, SHOW ERRORS, @warning_count,
- @error_count.
- </remark>
-
<para>
This appendix lists common problems and errors that may occur and
potential resolutions, in addition to listing the errors that may
@@ -35,6 +30,86 @@
</formalpara>
+ <section id="error-sources">
+
+ <title>Sources of Error Information</title>
+
+ <indexterm>
+ <primary>errors</primary>
+ <secondary>sources of information</secondary>
+ </indexterm>
+
+ <para>
+ There are several sources of error information in MySQL:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Each SQL statement executed results in an error code, an
+ SQLSTATE value, and an error message, as described in
+ <xref linkend="error-types"/>. These errors are returned from
+ the server side; see <xref linkend="error-messages-server"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Errors can occur on the client side, usually involving
+ problems communicating with the server; see
+ <xref linkend="error-messages-client"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ SQL statement warning and error information is available via
+ the <literal role="stmt">SHOW WARNINGS</literal> and
+ <literal role="stmt">SHOW ERRORS</literal> statements. The
+ <literal role="sysvar">warning_count</literal> and
+ <literal role="sysvar">error_count</literal> system variable
+ provide counts of the number of warnings and errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt">SHOW SLAVE STATUS</literal> statement
+ output includes information about replication errors occurring
+ on the slave side.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt" condition="show-engine">SHOW ENGINE
+ INNODB STATUS</literal> statement output includes information
+ about the most recent foreign key error if a
+ <literal role="stmt">CREATE TABLE</literal> statement for an
+ <literal role="se">InnoDB</literal> table fails.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <command>perror</command> program provides information
+ from the command line about error numbers. See
+ <xref linkend="perror"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Descriptions of server and client errors are provided later in
+ this Appendix. For information about errors related to
+ <literal role="se">InnoDB</literal>, see
+ <xref linkend="innodb-error-handling"/>.
+ </para>
+
+ </section>
+
<section id="error-types">
<title>Types of Error Values</title>
@@ -64,9 +139,13 @@
</itemizedlist>
<para>
+ A message string that provides a textual description of the error
+ is also available.
+ </para>
+
+ <para>
When an error occurs, you can access the MySQL error code, the
- SQLSTATE value, and a string containing an error message using C
- API functions:
+ SQLSTATE value, and the message string using C API functions:
</para>
<itemizedlist>
@@ -181,7 +260,8 @@
<listitem>
<para>
- A string that provides a textual description of the error.
+ A message string that provides a textual description of the
+ error.
</para>
</listitem>
Modified: trunk/refman-5.4/errors-problems-core.xml
===================================================================
--- trunk/refman-5.4/errors-problems-core.xml 2009-10-30 15:49:20 UTC (rev 17397)
+++ trunk/refman-5.4/errors-problems-core.xml 2009-10-30 16:24:09 UTC (rev 17398)
Changed blocks: 4, Lines Added: 88, Lines Deleted: 8; 3886 bytes
@@ -9,11 +9,6 @@
<remark role="dynamic-dependency-list"/>
- <remark role="todo">
- say something about SHOW WARNINGS, SHOW ERRORS, @warning_count,
- @error_count.
- </remark>
-
<para>
This appendix lists common problems and errors that may occur and
potential resolutions, in addition to listing the errors that may
@@ -35,6 +30,86 @@
</formalpara>
+ <section id="error-sources">
+
+ <title>Sources of Error Information</title>
+
+ <indexterm>
+ <primary>errors</primary>
+ <secondary>sources of information</secondary>
+ </indexterm>
+
+ <para>
+ There are several sources of error information in MySQL:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Each SQL statement executed results in an error code, an
+ SQLSTATE value, and an error message, as described in
+ <xref linkend="error-types"/>. These errors are returned from
+ the server side; see <xref linkend="error-messages-server"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Errors can occur on the client side, usually involving
+ problems communicating with the server; see
+ <xref linkend="error-messages-client"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ SQL statement warning and error information is available via
+ the <literal role="stmt">SHOW WARNINGS</literal> and
+ <literal role="stmt">SHOW ERRORS</literal> statements. The
+ <literal role="sysvar">warning_count</literal> and
+ <literal role="sysvar">error_count</literal> system variable
+ provide counts of the number of warnings and errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt">SHOW SLAVE STATUS</literal> statement
+ output includes information about replication errors occurring
+ on the slave side.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt" condition="show-engine">SHOW ENGINE
+ INNODB STATUS</literal> statement output includes information
+ about the most recent foreign key error if a
+ <literal role="stmt">CREATE TABLE</literal> statement for an
+ <literal role="se">InnoDB</literal> table fails.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <command>perror</command> program provides information
+ from the command line about error numbers. See
+ <xref linkend="perror"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Descriptions of server and client errors are provided later in
+ this Appendix. For information about errors related to
+ <literal role="se">InnoDB</literal>, see
+ <xref linkend="innodb-error-handling"/>.
+ </para>
+
+ </section>
+
<section id="error-types">
<title>Types of Error Values</title>
@@ -64,9 +139,13 @@
</itemizedlist>
<para>
+ A message string that provides a textual description of the error
+ is also available.
+ </para>
+
+ <para>
When an error occurs, you can access the MySQL error code, the
- SQLSTATE value, and a string containing an error message using C
- API functions:
+ SQLSTATE value, and the message string using C API functions:
</para>
<itemizedlist>
@@ -181,7 +260,8 @@
<listitem>
<para>
- A string that provides a textual description of the error.
+ A message string that provides a textual description of the
+ error.
</para>
</listitem>
Modified: trunk/refman-5.5/errors-problems-core.xml
===================================================================
--- trunk/refman-5.5/errors-problems-core.xml 2009-10-30 15:49:20 UTC (rev 17397)
+++ trunk/refman-5.5/errors-problems-core.xml 2009-10-30 16:24:09 UTC (rev 17398)
Changed blocks: 4, Lines Added: 88, Lines Deleted: 8; 3886 bytes
@@ -9,11 +9,6 @@
<remark role="dynamic-dependency-list"/>
- <remark role="todo">
- say something about SHOW WARNINGS, SHOW ERRORS, @warning_count,
- @error_count.
- </remark>
-
<para>
This appendix lists common problems and errors that may occur and
potential resolutions, in addition to listing the errors that may
@@ -35,6 +30,86 @@
</formalpara>
+ <section id="error-sources">
+
+ <title>Sources of Error Information</title>
+
+ <indexterm>
+ <primary>errors</primary>
+ <secondary>sources of information</secondary>
+ </indexterm>
+
+ <para>
+ There are several sources of error information in MySQL:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Each SQL statement executed results in an error code, an
+ SQLSTATE value, and an error message, as described in
+ <xref linkend="error-types"/>. These errors are returned from
+ the server side; see <xref linkend="error-messages-server"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Errors can occur on the client side, usually involving
+ problems communicating with the server; see
+ <xref linkend="error-messages-client"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ SQL statement warning and error information is available via
+ the <literal role="stmt">SHOW WARNINGS</literal> and
+ <literal role="stmt">SHOW ERRORS</literal> statements. The
+ <literal role="sysvar">warning_count</literal> and
+ <literal role="sysvar">error_count</literal> system variable
+ provide counts of the number of warnings and errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt">SHOW SLAVE STATUS</literal> statement
+ output includes information about replication errors occurring
+ on the slave side.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt" condition="show-engine">SHOW ENGINE
+ INNODB STATUS</literal> statement output includes information
+ about the most recent foreign key error if a
+ <literal role="stmt">CREATE TABLE</literal> statement for an
+ <literal role="se">InnoDB</literal> table fails.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <command>perror</command> program provides information
+ from the command line about error numbers. See
+ <xref linkend="perror"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Descriptions of server and client errors are provided later in
+ this Appendix. For information about errors related to
+ <literal role="se">InnoDB</literal>, see
+ <xref linkend="innodb-error-handling"/>.
+ </para>
+
+ </section>
+
<section id="error-types">
<title>Types of Error Values</title>
@@ -64,9 +139,13 @@
</itemizedlist>
<para>
+ A message string that provides a textual description of the error
+ is also available.
+ </para>
+
+ <para>
When an error occurs, you can access the MySQL error code, the
- SQLSTATE value, and a string containing an error message using C
- API functions:
+ SQLSTATE value, and the message string using C API functions:
</para>
<itemizedlist>
@@ -181,7 +260,8 @@
<listitem>
<para>
- A string that provides a textual description of the error.
+ A message string that provides a textual description of the
+ error.
</para>
</listitem>
Modified: trunk/refman-6.0.sav/errors-problems.xml
===================================================================
--- trunk/refman-6.0.sav/errors-problems.xml 2009-10-30 15:49:20 UTC (rev 17397)
+++ trunk/refman-6.0.sav/errors-problems.xml 2009-10-30 16:24:09 UTC (rev 17398)
Changed blocks: 4, Lines Added: 88, Lines Deleted: 8; 3898 bytes
@@ -7,11 +7,6 @@
<title>Errors, Error Codes, and Common Problems</title>
- <remark role="todo">
- say something about SHOW WARNINGS, SHOW ERRORS, @warning_count,
- @error_count.
- </remark>
-
<para>
This appendix lists common problems and errors that may occur and
potential resolutions, in addition to listing the errors that may
@@ -33,6 +28,86 @@
</formalpara>
+ <section id="error-sources">
+
+ <title>Sources of Error Information</title>
+
+ <indexterm>
+ <primary>errors</primary>
+ <secondary>sources of information</secondary>
+ </indexterm>
+
+ <para>
+ There are several sources of error information in MySQL:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Each SQL statement executed results in an error code, an
+ SQLSTATE value, and an error message, as described in
+ <xref linkend="error-types"/>. These errors are returned from
+ the server side; see <xref linkend="error-messages-server"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Errors can occur on the client side, usually involving
+ problems communicating with the server; see
+ <xref linkend="error-messages-client"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ SQL statement warning and error information is available via
+ the <literal role="stmt">SHOW WARNINGS</literal> and
+ <literal role="stmt">SHOW ERRORS</literal> statements. The
+ <literal role="sysvar">warning_count</literal> and
+ <literal role="sysvar">error_count</literal> system variable
+ provide counts of the number of warnings and errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt">SHOW SLAVE STATUS</literal> statement
+ output includes information about replication errors occurring
+ on the slave side.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal role="stmt" condition="show-engine">SHOW ENGINE
+ INNODB STATUS</literal> statement output includes information
+ about the most recent foreign key error if a
+ <literal role="stmt">CREATE TABLE</literal> statement for an
+ <literal role="se">InnoDB</literal> table fails.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <command>perror</command> program provides information
+ from the command line about error numbers. See
+ <xref linkend="perror"/>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Descriptions of server and client errors are provided later in
+ this Appendix. For information about errors related to
+ <literal role="se">InnoDB</literal>, see
+ <xref linkend="innodb-error-handling"/>.
+ </para>
+
+ </section>
+
<section id="error-types">
<title>Types of Error Values</title>
@@ -62,9 +137,13 @@
</itemizedlist>
<para>
+ A message string that provides a textual description of the error
+ is also available.
+ </para>
+
+ <para>
When an error occurs, you can access the MySQL error code, the
- SQLSTATE value, and a string containing an error message using C
- API functions:
+ SQLSTATE value, and the message string using C API functions:
</para>
<itemizedlist>
@@ -179,7 +258,8 @@
<listitem>
<para>
- A string that provides a textual description of the error.
+ A message string that provides a textual description of the
+ error.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r17398 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0.sav | paul.dubois | 30 Oct |
