Sean Chittenden <[EMAIL PROTECTED]> writes:
>> ... it should have a SQLSTATE assigned, so you could
>> check for ERRCODE_INVALID_AUTHORIZATION_SPECIFICATION ...
> Ok, I've read over the code a little bit... it doesn't seem like
> there's an obvious way to get the error code via libpq(3).
Hmmm ... I was thinking of PQresultErrorField, but you don't actually
get a PGresult from a connection failure, so that's no good :-(.
I suppose we need to think about extending libpq so that a SQLSTATE
can be retrieved for connection-level failures. That kinda moves
it out of the realm of bug-fix-for-beta though.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
