1
1
<!--
2
- $Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.52 2003/09/20 20:12:04 tgl Exp $
2
+ $Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.53 2003/10/17 18:57:00 tgl Exp $
3
3
-->
4
4
5
5
<chapter id="ecpg">
@@ -1151,13 +1151,13 @@ struct
1151
1151
two characters indicate the general class of the condition, the
1152
1152
last three characters indicate a subclass of the general
1153
1153
condition. A successful state is indicated by the code
1154
- <literal>00000</literal>. Further information about the codes can
1155
- be found XXX. The <literal>SQLSTATE</literal> codes are for the
1156
- most part defined in the SQL standard. The
1154
+ <literal>00000</literal>. The <literal>SQLSTATE</literal> codes are for
1155
+ the most part defined in the SQL standard. The
1157
1156
<productname>PostgreSQL</productname> server natively supports
1158
1157
<literal>SQLSTATE</literal> error codes; therefore a high degree
1159
1158
of consistency can be achieved by using this error code scheme
1160
- throughout all applications.
1159
+ throughout all applications. For further information see
1160
+ <xref linkend="errcodes-appendix">.
1161
1161
</para>
1162
1162
1163
1163
<para>
@@ -1178,7 +1178,8 @@ struct
1178
1178
<literal>SQLSTATE</literal> is also listed. There is, however, no
1179
1179
one-to-one or one-to-many mapping between the two schemes (indeed
1180
1180
it is many-to-many), so you should consult the global
1181
- <literal>SQLSTATE</literal> listing in XXX in each case.
1181
+ <literal>SQLSTATE</literal> listing in <xref linkend="errcodes-appendix">
1182
+ in each case.
1182
1183
</para>
1183
1184
1184
1185
<para>
0 commit comments