Author: pd221994
Date: 2011-02-24 19:18:15 +0100 (Thu, 24 Feb 2011)
New Revision: 25146
Log:
r45277@dhcp-adc-twvpn-1-vpnpool-10-154-16-118: paul | 2011-02-24 11:16:40 -0500
Add note about stability of error codes/messages
Modified:
svk:merge
trunk/refman-5.0/errors-problems.xml
trunk/refman-5.1/errors-problems.xml
trunk/refman-5.5/errors-problems.xml
trunk/refman-5.6/errors-problems.xml
trunk/refman-6.0/errors-problems.xml
Property changes on: trunk
___________________________________________________________________
Modified: svk:merge
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 1277 bytes
Modified: trunk/refman-5.0/errors-problems.xml
===================================================================
--- trunk/refman-5.0/errors-problems.xml 2011-02-24 15:38:19 UTC (rev 25145)
+++ trunk/refman-5.0/errors-problems.xml 2011-02-24 18:18:15 UTC (rev 25146)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 0; 984 bytes
@@ -254,6 +254,19 @@
</itemizedlist>
<para>
+ For error checking, use error codes, not error messages. Error
+ messages do not change often, but it is possible. Also if the
+ database administrator changes the language setting, that affects
+ the language of error messages.
+ </para>
+
+ <para>
+ Error codes are stable across GA releases of a given MySQL series.
+ Before a series reaches GA status, new codes may still be under
+ development and subject to change.
+ </para>
+
+ <para>
Server error information comes from the following source files.
For details about the way that error information is defined, see
the MySQL Internals manual, available at
Modified: trunk/refman-5.1/errors-problems.xml
===================================================================
--- trunk/refman-5.1/errors-problems.xml 2011-02-24 15:38:19 UTC (rev 25145)
+++ trunk/refman-5.1/errors-problems.xml 2011-02-24 18:18:15 UTC (rev 25146)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 0; 984 bytes
@@ -254,6 +254,19 @@
</itemizedlist>
<para>
+ For error checking, use error codes, not error messages. Error
+ messages do not change often, but it is possible. Also if the
+ database administrator changes the language setting, that affects
+ the language of error messages.
+ </para>
+
+ <para>
+ Error codes are stable across GA releases of a given MySQL series.
+ Before a series reaches GA status, new codes may still be under
+ development and subject to change.
+ </para>
+
+ <para>
Server error information comes from the following source files.
For details about the way that error information is defined, see
the MySQL Internals manual, available at
Modified: trunk/refman-5.5/errors-problems.xml
===================================================================
--- trunk/refman-5.5/errors-problems.xml 2011-02-24 15:38:19 UTC (rev 25145)
+++ trunk/refman-5.5/errors-problems.xml 2011-02-24 18:18:15 UTC (rev 25146)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 0; 984 bytes
@@ -254,6 +254,19 @@
</itemizedlist>
<para>
+ For error checking, use error codes, not error messages. Error
+ messages do not change often, but it is possible. Also if the
+ database administrator changes the language setting, that affects
+ the language of error messages.
+ </para>
+
+ <para>
+ Error codes are stable across GA releases of a given MySQL series.
+ Before a series reaches GA status, new codes may still be under
+ development and subject to change.
+ </para>
+
+ <para>
Server error information comes from the following source files.
For details about the way that error information is defined, see
the MySQL Internals manual, available at
Modified: trunk/refman-5.6/errors-problems.xml
===================================================================
--- trunk/refman-5.6/errors-problems.xml 2011-02-24 15:38:19 UTC (rev 25145)
+++ trunk/refman-5.6/errors-problems.xml 2011-02-24 18:18:15 UTC (rev 25146)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 0; 984 bytes
@@ -254,6 +254,19 @@
</itemizedlist>
<para>
+ For error checking, use error codes, not error messages. Error
+ messages do not change often, but it is possible. Also if the
+ database administrator changes the language setting, that affects
+ the language of error messages.
+ </para>
+
+ <para>
+ Error codes are stable across GA releases of a given MySQL series.
+ Before a series reaches GA status, new codes may still be under
+ development and subject to change.
+ </para>
+
+ <para>
Server error information comes from the following source files.
For details about the way that error information is defined, see
the MySQL Internals manual, available at
Modified: trunk/refman-6.0/errors-problems.xml
===================================================================
--- trunk/refman-6.0/errors-problems.xml 2011-02-24 15:38:19 UTC (rev 25145)
+++ trunk/refman-6.0/errors-problems.xml 2011-02-24 18:18:15 UTC (rev 25146)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 0; 984 bytes
@@ -254,6 +254,19 @@
</itemizedlist>
<para>
+ For error checking, use error codes, not error messages. Error
+ messages do not change often, but it is possible. Also if the
+ database administrator changes the language setting, that affects
+ the language of error messages.
+ </para>
+
+ <para>
+ Error codes are stable across GA releases of a given MySQL series.
+ Before a series reaches GA status, new codes may still be under
+ development and subject to change.
+ </para>
+
+ <para>
Server error information comes from the following source files.
For details about the way that error information is defined, see
the MySQL Internals manual, available at
| Thread |
|---|
| • svn commit - mysqldoc@oter02: r25146 - in trunk: . refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0 | paul.dubois | 24 Feb |
