FairCom DB V12 Release Notes

ctdbGetRecordKeyPos no longer causes ctdbNextRecord unexpected behavior on partitioned files

Unexpected behavior was seen on partitioned files:

• When ctdbGetRecordKeyPos() was called during an index scan on a partitioned file, the scan never terminated.
• Independent index scans with different record handles (or ISAM contexts) using a partition index could return an incorrect number of search results (too few or too many).

The logic has been modified to correct this behavior.

Note: ISAM applications using a partition index must be aware that a low-level key search on the same index could modify the internal state of their current ISAM context. This does not happen with non-partition files. To avoid unexpected behavior, such low level operations must occur within a separate ISAM context.