Re: BUG #5753: Existing Functions No Longer Work

On Tue, Nov 16, 2010 at 5:13 PM, Kris Jurka <books@ejurka.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? =A0Like something from EnterpriseDB? =A0I=
t 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. =A0This thread is too confusing =
with
> random snippets, assertions, and differences between pgadmin, psql, and
> other interfaces to tell what's really going on. =A0The behavior of the J=
DBC
> driver shouldn't have changed between releases either, but this may expla=
in
> the differences seen between pgadmin and the user's application.
>
> http://jdbc.postgresql.org/documentation/84/callproc.html#callproc-result=
set-refcursor

This seems likely to be related to the OP's problem, because his code
snippet does in fact show him calling getObject()...

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company