db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Korneliussen <Andreas.Kornelius...@Sun.COM>
Subject Re: [jira] Updated: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset
Date Mon, 28 Aug 2006 10:58:30 GMT
Mike Matrigali wrote:
> 
> 
> Andreas Korneliussen (JIRA) wrote:
>>      [ http://issues.apache.org/jira/browse/DERBY-1696?page=all ]
>>
>> Andreas Korneliussen updated DERBY-1696:
>> ----------------------------------------
>>
>>     Component/s: Store
>>
>> To fix this issue, I need a mechanism to notify the store
>> (scancontroller) to move off the row (i.e to afterLast() or
>> beforeFirst()), so that it can release the lock on the current row.
>>
>> I do consider the following options:
>>
>> Alternative 1: Use the method
>> ScanController.positionAtRowLocation(RowLocation rl)
>>
>> Here the RowLocation objects could represent the positions beforeFirst
>> and afterLast. I.e one could make use of the RecordHandle.
>> RESERVED4_RECORD_HANDLE and
>> RecordHandle. RESERVED4_RECORD_HANDLE to represent to beforeFirst and
>> afterLast positions.
>>
>> When the method ScanController.positionAtRowLocation(RowLocation rl),
>> is called with a rowlocation with these  positions,
>> the scan implementation may release the U-lock of the current row
>>
>> Alternative 2:
>> Add new methods to ScanController interface: moveToAfterLast() and
>> moveToBeforeFirst()
> 
> Can you just close the scan if you don't need it positioned anymore?

I'll check if that works

Regards
Andreas


Mime
View raw message