From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Korry Douglas <korry(dot)douglas(at)enterprisedb(dot)com>, vince maxey <vamax27(at)yahoo(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5753: Existing Functions No Longer Work |
Date: | 2010-11-18 02:50:11 |
Message-ID: | AANLkTimw4vNoGBE9+pJgvmLaDodyw7GM6MNuNnvRVR4G@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Nov 16, 2010 at 5:13 PM, Kris Jurka <books(at)ejurka(dot)com> wrote:
> On Tue, 16 Nov 2010, Korry Douglas wrote:
>
>> Vince - is there any chance that you were using a non-standard PostgreSQL
>> distribution or driver before? Like something from EnterpriseDB? It may be
>> that a third-party JDBC driver was doing some behind-the-curtains work on
>> your behalf.
>>
>
> The stock JDBC driver does have support for refcursors, so that it will do
> FETCH ALL FROM it and return a ResultSet object instead of just a string if
> you call getObject on a refcursor value. This thread is too confusing with
> random snippets, assertions, and differences between pgadmin, psql, and
> other interfaces to tell what's really going on. The behavior of the JDBC
> driver shouldn't have changed between releases either, but this may explain
> the differences seen between pgadmin and the user's application.
>
> http://jdbc.postgresql.org/documentation/84/callproc.html#callproc-resultset-refcursor
This seems likely to be related to the OP's problem, because his code
snippet does in fact show him calling getObject()...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-11-18 02:54:33 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
Previous Message | Tom Lane | 2010-11-17 22:23:54 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |