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: conflict detection strategies
Date Wed, 15 Feb 2006 16:12:22 GMT

>> I think there are other situations where the RowLocation will become
>> invalid, such as the transaction deleteing the row.
>>
> 
> Yes, however as far as I understood, the RowLocation would not be reused 
> as long as at least some sort of table level intent lock is held, and 
> the store will simply return false if one tries to do update / delete / 
> fetch on a RowLocation which is deleted, or deleted+purged.
>

To be clear: we do handle the situation were RowLocation points to a 
deleted row by giving a WARNING if the user tries to do updateRow() or 
deleteRow(). For positioned updates, we will give an update count of 0. 
Therefore we do not really think of those RowLocations as invalid.


Andreas


> Andreas


Mime
View raw message