Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior
Date
Msg-id 13237.1260999558@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior  (Chris Travers <chris@metatrontech.com>)
Responses Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior  (Chris Travers <chris@metatrontech.com>)
List pgsql-bugs
Chris Travers <chris@metatrontech.com> writes:
> trying again.  Sorry for the duplicate.
> On Wed, Dec 16, 2009 at 1:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Exactly what "frontend" are you talking about here?  Because what this
>> sounds like to me is a client-side programming error.  It's certainly
>> not the backend's fault, and I doubt it is libpq's either.

> I am using DBD::Pg.

> I asked about it on #postgresql and was told this was the SQLSTATE code
> passed up from libpq (by the author of DBD::Pg).  Several other folks
> there seemed to concur.

Could you provide a self-contained test case?  And what versions of
DBD::Pg etc are we talking about?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Chris Travers
Date:
Subject: Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior
Next
From: Robert Haas
Date:
Subject: Re: Invalid explain output for multi-plan statements