Commit e5c2c978 authored by Tom Lane's avatar Tom Lane

Add a listing of our SQLSTATE error codes to the documentation.

Link to it from some appropriate places.
parent 34ed5059
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.52 2003/09/20 20:12:04 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.53 2003/10/17 18:57:00 tgl Exp $
--> -->
<chapter id="ecpg"> <chapter id="ecpg">
...@@ -1151,13 +1151,13 @@ struct ...@@ -1151,13 +1151,13 @@ struct
two characters indicate the general class of the condition, the two characters indicate the general class of the condition, the
last three characters indicate a subclass of the general last three characters indicate a subclass of the general
condition. A successful state is indicated by the code condition. A successful state is indicated by the code
<literal>00000</literal>. Further information about the codes can <literal>00000</literal>. The <literal>SQLSTATE</literal> codes are for
be found XXX. The <literal>SQLSTATE</literal> codes are for the the most part defined in the SQL standard. The
most part defined in the SQL standard. The
<productname>PostgreSQL</productname> server natively supports <productname>PostgreSQL</productname> server natively supports
<literal>SQLSTATE</literal> error codes; therefore a high degree <literal>SQLSTATE</literal> error codes; therefore a high degree
of consistency can be achieved by using this error code scheme of consistency can be achieved by using this error code scheme
throughout all applications. throughout all applications. For further information see
<xref linkend="errcodes-appendix">.
</para> </para>
<para> <para>
...@@ -1178,7 +1178,8 @@ struct ...@@ -1178,7 +1178,8 @@ struct
<literal>SQLSTATE</literal> is also listed. There is, however, no <literal>SQLSTATE</literal> is also listed. There is, however, no
one-to-one or one-to-many mapping between the two schemes (indeed one-to-one or one-to-many mapping between the two schemes (indeed
it is many-to-many), so you should consult the global it is many-to-many), so you should consult the global
<literal>SQLSTATE</literal> listing in XXX in each case. <literal>SQLSTATE</literal> listing in <xref linkend="errcodes-appendix">
in each case.
</para> </para>
<para> <para>
......
This diff is collapsed.
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/filelist.sgml,v 1.30 2003/09/01 23:01:49 petere Exp $ --> <!-- $Header: /cvsroot/pgsql/doc/src/sgml/filelist.sgml,v 1.31 2003/10/17 18:57:01 tgl Exp $ -->
<!entity history SYSTEM "history.sgml"> <!entity history SYSTEM "history.sgml">
<!entity info SYSTEM "info.sgml"> <!entity info SYSTEM "info.sgml">
...@@ -23,6 +23,7 @@ ...@@ -23,6 +23,7 @@
<!entity datetime SYSTEM "datetime.sgml"> <!entity datetime SYSTEM "datetime.sgml">
<!entity ddl SYSTEM "ddl.sgml"> <!entity ddl SYSTEM "ddl.sgml">
<!entity dml SYSTEM "dml.sgml"> <!entity dml SYSTEM "dml.sgml">
<!entity errcodes SYSTEM "errcodes.sgml">
<!entity features SYSTEM "features.sgml"> <!entity features SYSTEM "features.sgml">
<!entity func SYSTEM "func.sgml"> <!entity func SYSTEM "func.sgml">
<!entity indices SYSTEM "indices.sgml"> <!entity indices SYSTEM "indices.sgml">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.139 2003/10/04 21:05:20 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.140 2003/10/17 18:57:01 tgl Exp $
--> -->
<chapter id="libpq"> <chapter id="libpq">
...@@ -1332,8 +1332,8 @@ localized translation of one of these. Always present. ...@@ -1332,8 +1332,8 @@ localized translation of one of these. Always present.
</term> </term>
<listitem> <listitem>
<para> <para>
The SQLSTATE code for the error (a 5-character string following SQL The SQLSTATE code for the error (see <xref linkend="errcodes-appendix">).
spec conventions). Not localizable. Always present. Not localizable. Always present.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.56 2003/09/12 22:17:23 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.57 2003/10/17 18:57:01 tgl Exp $
--> -->
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [ <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
...@@ -244,6 +244,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.56 2003/09/12 22:17:23 tg ...@@ -244,6 +244,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.56 2003/09/12 22:17:23 tg
<part id="appendixes"> <part id="appendixes">
<title>Appendixes</title> <title>Appendixes</title>
&errcodes;
&datetime; &datetime;
&keywords; &keywords;
&features; &features;
......
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.45 2003/09/20 20:12:05 tgl Exp $ --> <!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.46 2003/10/17 18:57:01 tgl Exp $ -->
<chapter id="protocol"> <chapter id="protocol">
<title>Frontend/Backend Protocol</title> <title>Frontend/Backend Protocol</title>
...@@ -3833,9 +3833,8 @@ message. ...@@ -3833,9 +3833,8 @@ message.
</Term> </Term>
<ListItem> <ListItem>
<Para> <Para>
Code: the SQLSTATE code for the error (a 5-character Code: the SQLSTATE code for the error (see <xref
string following SQL spec conventions). Not localizable. linkend="errcodes-appendix">). Not localizable. Always present.
Always present.
</Para> </Para>
</ListItem> </ListItem>
</VarListEntry> </VarListEntry>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment