Sorry about that, I missed your comment:
To cursors (without hold) disappear at transaction end. You need to
ensure you have done Connection.setAutoCommit(false) or else the cursor
will disappear before you can fetch from it.
So, you saying that when I create my original database connection,
I need to set Connection.setAutoCommit(false)
I have not seen that in any of the examples/tutorials I have looked at.
I would expect that to have an effect on updating the database, not fetching
from the database.
How will that affect other stored procedure fetches?
Kris Jurka wrote:
>
>
>
> On Thu, 25 Sep 2008, burferd wrote:
>
>> Thanks for the fast feedback, but changing the type to OTHER does not
>> resolve the problem, I still get the same error.
>
> That was just mentioned in passing for future compatibility, not the real
> problem. As I stated before the real issue is your autocommit setting.
>
> Kris Jurka
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
>
--
View this message in context: http://www.nabble.com/Newby-Question---accessing-refcursor.-tp19680083p19681449.html
Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.
