Re: Refcursor bug

From: Altaf Malik <mmalik_altaf(at)yahoo(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Refcursor bug
Date: 2007-04-27 17:56:32
Message-ID: 704996.38286.qm@web39113.mail.mud.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Yes it is useless but at least we cannot prevent the user from doing it. Does it mean we should throw exception and not allow user to get even the first resultset? Because exception comes internally when processing the resultset.

--Altaf

Kris Jurka <books(at)ejurka(dot)com> wrote:

On Fri, 27 Apr 2007, Altaf Malik wrote:

> Hi, I encountered a bug with refcursors with the latest JDBC driver. I
> cannot get two refcursors as OUT parameter if both of them point to the
> same underlying refcursor.
>

Is this an actual problem or just something you came up with to make it
fail? I don't see the use case here because the previous driver version
would return the full ResultSet and then an empty one because everything
had been fetched from it. So that would be pretty useless.

Kris Jurka

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend


---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2007-04-27 18:50:21 Re: Refcursor bug
Previous Message Kris Jurka 2007-04-27 17:34:41 Re: Refcursor bug