|
|
|
Error 160 could occur when reading a record that was added using c-treeDB if the record's last field was a length-counted string data type (CT_PSTRING, CT_2STRING, or CT_4STRING) that had an index segment that used the Unicode key segment mode (UNCSEG) with extended key segment source type of ctKSEG_STYP_PROVIDED or ctKSEG_STYP_UTF8, and the field data had zero length.
Other possible symptoms include: error INOT_ERR (101) when searching for a key matching a particular value, error KDUP_ERR (2) when adding a record, and the wrong collation (ordering) of key values.
The logic has been corrected to handles this situation properly.
