Thanks for your reply,
> FATAL is probably a bad choice of words here; it basically means any
> error condition reported by the server that caused execution of your
> query to be abandoned. NONFATAL_ERROR actually means "notice or
> warning message", and isn't a possible return code from PQexec a
[EMAIL PROTECTED] writes:
> My question is, what constitutes a PGRES_FATAL_ERROR or a
> PGRES_BAD_RESPONSE?
FATAL is probably a bad choice of words here; it basically means any
error condition reported by the server that caused execution of your
query to be abandoned. NONFATAL_ERROR actually mean
On May 23 11:30, [EMAIL PROTECTED] wrote:
> I'm currently trying to understand how to deal with the return values
> of PGresultStatus in terms of error handling in my application. The
> postgres manual describes the return codes of PGresultStatus as:
>
> PGRES_EMPTY_QUERY: The string sent to the
[EMAIL PROTECTED] wrote:
> I'm currently trying to understand how to deal with the return values
> of PGresultStatus in terms of error handling in my application. The
> postgres manual describes the return codes of PGresultStatus as:
>
> PGRES_EMPTY_QUERY: The string sent to the server was empty
I'm currently trying to understand how to deal with the return values
of PGresultStatus in terms of error handling in my application. The
postgres manual describes the return codes of PGresultStatus as:
PGRES_EMPTY_QUERY: The string sent to the server was empty.
PGRES_COMMAND_OK: Successful co
