Re: [Erserver-general] Why does Statement.close() close result

Barry Lind wrote:

> Jan Wieck wrote:
>> How is the automatic cursor code controlled by setFetchSize() affected
>> by a Statement.close() before the result set is consumed? Does that need
>> to use holdable cursors here because in turn the transaction around the
>> cursor could end sooner than expected?
>>
>>
>> Jan
>>
>
> This is an interesting question. The current logic for cursor backed
> result sets will error if you try to access the result set after a
> commit/rollback (actually you will get an error when you exhaust the
> already fetched values that are in memory and try to fetch more from the
> database).

Only >= 7.4. Everything before just gives a NOTICE but otherwise just
returns "FETCH 0" or "CLOSE" as if the cursor would exist. It does that
even for cursors that have never been declared.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #