From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Question about refcursors |
Date: | 2007-10-26 23:20:22 |
Message-ID: | Pine.BSO.4.64.0710261917500.19968@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Sat, 27 Oct 2007, Thomas Kellerer wrote:
> Now after running the procedure (using execute()) I'm (generically) calling
> getResultSet() on the statement object. And indeed the driver does return a
> ResultSet, but it seems that the actual result of the call is "hidden" inside
> one of the columns of the resultset. If I do a getObject() on that resultset
> I get another result set which indeed is the result of my SELECT in the
> procedure.
>
> My question: is there a reason why the "real" result cannot be obtained using
> getResultSet() but is wrapped into another ResultSet?
>
Consider what should be returned by:
SELECT 1, 'some text', func_returning_refcursor();
Or a function returning a refcursor as an out parameter.
Or a function returning a setof refcursor.
Just like you don't know exactly what you're executing, neither does the
driver.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2007-10-26 23:25:27 | Re: Question about refcursors |
Previous Message | Thomas Kellerer | 2007-10-26 22:55:35 | Question about refcursors |