Hi,
i ask here to not spam into the tracker.
I know that indexes in Firebird are not transactional objects.
My understanding was that when we update record
then old record vesion go to new place and new record version replace place
where old record version was.
This prevent for updating index entry when nothing in the indexed fields was
changed.
But now i read that:
>> So, many years ago (when FB 2.0 was developed, iirc), algorithm above was
>> changed a bit - since then Firebird
>> engine adds index key despite of its presence with the same record number.
>> This could lead to the non-removable keys but it is much less evil than
>> missed entries.
do i understand correctly that now it store new entry always?
And it store with link to the same record not to old record version?
>> This doesn't work in concurrent environment, unfortunately, and could
>> produce index with missed entries (which is
>> very serious problem). I don't want to go too deep into details here.
Maybe you can bring light here if not on the tracker?
>> So far i have no good solution for this problem.
if described in details, more heads can got some concept how to solve this.
regards,
Karol Bieniaszewski
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
