| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kris Jurka <books(at)ejurka(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Removing our datasource/pooling implementation. |
| Date: | 2005-01-15 07:54:24 |
| Message-ID: | 41E8CC30.4060601@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Tom Lane wrote:
> Oliver Jowett <oliver(at)opencloud(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen McConnell | 2005-01-15 19:57:03 | Re: An I/O error occured while sending to the backend. |
| Previous Message | Oliver Jowett | 2005-01-15 07:27:45 | Re: Weird behavior in transaction handling (Possible bug ?) |