11<!--
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 $
33-->
44
55<chapter id="ecpg">
@@ -1151,13 +1151,13 @@ struct
11511151 two characters indicate the general class of the condition, the
11521152 last three characters indicate a subclass of the general
11531153 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
11571156 <productname>PostgreSQL</productname> server natively supports
11581157 <literal>SQLSTATE</literal> error codes; therefore a high degree
11591158 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">.
11611161 </para>
11621162
11631163 <para>
@@ -1178,7 +1178,8 @@ struct
11781178 <literal>SQLSTATE</literal> is also listed. There is, however, no
11791179 one-to-one or one-to-many mapping between the two schemes (indeed
11801180 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.
11821183 </para>
11831184
11841185 <para>