Re: Removing our datasource/pooling implementation. - Mailing list pgsql-jdbc

From Oliver Jowett
Subject Re: Removing our datasource/pooling implementation.
Date
Msg-id 41E8CC30.4060601@opencloud.com
Whole thread Raw
In response to Re: Removing our datasource/pooling implementation.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc
Tom Lane wrote:
> Oliver Jowett <oliver@opencloud.com> writes:
>
>>Some of the SQL states I assigned aren't very good matches. The main one
>>is that "you can't do that operation on that sort of object" type of
>>error is mapped to "object not in prerequisite state". Any better ideas?
>
>
> ERRCODE_WRONG_OBJECT_TYPE (42809) seems like a better match.  The
> prerequisite-state error implies that you could have done that operation
> on that object, if it were in a more receptive mood.

Thanks, that seems like a better match; I've changed most occurrences.
There were a couple of cases where "not in prerequisite state" was
closer, e.g. when trying to use a closed object.

-O

pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Weird behavior in transaction handling (Possible bug ?)
Next
From: Stephen McConnell
Date:
Subject: Re: An I/O error occured while sending to the backend.