| From: | Bart Lengkeek <bart(at)lengkeek(dot)com> |
|---|---|
| To: | pgsql-docs(at)postgresql(dot)org |
| Subject: | error fields |
| Date: | 2018-02-15 09:01:30 |
| Message-ID: | CAAdeC9TPYV+cgNLtGWoMqUiD+CS6WCVvdLknsLP_gGTogFDY2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2018-02-15 17:43:18 | The example for creating a check constraint is missing a comma |
| Previous Message | David G. Johnston | 2018-02-12 14:47:31 | Re: complex documentation and hard to find the reference |