Skip site navigation (1) Skip section navigation (2)

Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Travers <chris(at)metatrontech(dot)com>
Cc: Chris Travers <chris(dot)travers(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior
Date: 2009-12-16 21:39:18
Message-ID: 13237.1260999558@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Chris Travers <chris(at)metatrontech(dot)com> writes:
> trying again.  Sorry for the duplicate.
> On Wed, Dec 16, 2009 at 1:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: Robert HaasDate: 2009-12-16 22:17:36
Subject: Re: Invalid explain output for multi-plan statements
Previous:From: Chris TraversDate: 2009-12-16 21:16:12
Subject: Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group