On 02.10.13 00:20, mike matrigali wrote:
I don't have any good answers here, but maybe some places to look - and
some questions.
Are you going to ever need RowLocations of rows in an index? If so this
is going to be very new territory and Derby has never done that. For a
btree the RowLocation would be just the actual row as the location is
definined by the key - there is no other quick way given regular row
level locking as the row is free to move from page to page and slot to
slot. The abstraction of RowLocation was designed to handle this as
we wanted to be able to support a btree base table if necessary, but
no actual implementation was ever done.
Hi Mike,
Out of curiosity, would that btree base table be anything similar to an
Index Organized Table (IOT) in Oracle?
(I'm sure other products have similar, but nonetheless all to some
degree different from each other, constructs)
Regards,
--
Kristian
< snip >
