| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
| Cc: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SQLSTATE of notice PGresult |
| Date: | 2010-08-25 00:19:40 |
| Message-ID: | AANLkTinssi=Mv59sv6rsHBZxSqn+WwCtzMS4HpHijJ-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 20, 2010 at 11:05 AM, Euler Taveira de Oliveira
<euler(at)timbira(dot)com> wrote:
> Dmitriy Igrishin escreveu:
>> /* NOT presents - NULL. Why not "00000" ? */
>> const char* sqlstate = Pg::PQresultErrorField(res, PG_DIAG_SQLSTATE);
>>
> That's because the protocol doesn't set error field when the command
> succeeded. IMHO it's an oversight (the documentation is correct but the code
> is not) and should be correct because the spec enforces it.
Seems like a waste of bytes.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2010-08-25 00:43:16 | Re: security hook on authorization |
| Previous Message | Robert Haas | 2010-08-25 00:18:19 | Re: gSoC add MERGE command new patch -- merge_v104 |