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

Re: BUG #5753: Existing Functions No Longer Work

From: Kris Jurka <books(at)ejurka(dot)com>
To: Korry Douglas <korry(dot)douglas(at)enterprisedb(dot)com>
Cc: 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-16 22:13:52
Message-ID: alpine.BSO.2.00.1011161707440.25693@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-bugs

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

Kris Jurka

In response to

Responses

pgsql-bugs by date

Next:From: Elliott GroszekDate: 2010-11-16 22:39:07
Subject: BUG #5755: Query Optimzer Bug
Previous:From: Korry DouglasDate: 2010-11-16 21:52:48
Subject: Re: BUG #5753: Existing Functions No Longer Work

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