Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Re: SQLSTATE of notice PGresult
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
In response to
- Re: SQLSTATE of notice PGresult at 2010-08-20 15:05:06 from Euler Taveira de Oliveira
Responses
- Re: SQLSTATE of notice PGresult at 2010-08-25 01:44:10 from Euler Taveira de Oliveira
pgsql-hackers by date
Next: From: KaiGai Kohei Date: 2010-08-25 00:43:16 Subject: Re: security hook on authorization Previous: From: Robert Haas Date: 2010-08-25 00:18:19 Subject: Re: gSoC add MERGE command new patch -- merge_v104