MIME-Version: 1.0
Sender: bart@lengkeek.net
From: Bart Lengkeek <bart@lengkeek.com>
Date: Thu, 15 Feb 2018 10:01:30 +0100
Message-ID: 
 <CAAdeC9TPYV+cgNLtGWoMqUiD+CS6WCVvdLknsLP_gGTogFDY2g@mail.gmail.com>
Subject: error fields
To: pgsql-docs@postgresql.org
Content-Type: multipart/alternative; boundary="f4030436ea7449e05605653c7932"
Precedence: bulk

--f4030436ea7449e05605653c7932
Content-Type: text/plain; charset="UTF-8"

Hello doc keepers,


There is a minor incorrect statement in the libpq docs at following page.
https://www.postgresql.org/docs/devel/static/libpq-exec.html

Where it mentions PG_DIAG_SQLSTATE, in the documentation of the
PQresultErrorField, it says ".. is always present". But as I found out, and
verified after checking the source ( see comment at
https://doxygen.postgresql.org/fe-exec_8c_source.html#l00849 ), that isn't
true for libpq internal notices, which for example occur in a column out of
range situation.


Regards,

Bart Lengkeek

--f4030436ea7449e05605653c7932
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div>Hello doc keepers,<br><br><br></d=
iv>There is a minor incorrect statement in the libpq docs at following page=
. <a href=3D"https://www.postgresql.org/docs/devel/static/libpq-exec.html">=
https://www.postgresql.org/docs/devel/static/libpq-exec.html</a><br><br></d=
iv>Where it mentions PG_DIAG_SQLSTATE, in the documentation of the PQresult=
ErrorField, it says &quot;.. is always present&quot;. But as I found out, a=
nd verified after checking the source ( see comment at <a href=3D"https://d=
oxygen.postgresql.org/fe-exec_8c_source.html#l00849">https://doxygen.postgr=
esql.org/fe-exec_8c_source.html#l00849</a> ), that isn&#39;t true for libpq=
 internal notices, which for example occur in a column out of range situati=
on.<br><br></div><br></div>Regards,<br><br></div>Bart Lengkeek<br></div>

--f4030436ea7449e05605653c7932--