|
|
|
Error 160 (ITIM_ERR) was seen while reading Unicode records when the key contained a UNCSEG segment on a CT_FSTRING field, the content was not terminated with '\0', and kseg was configured as follows:
pkdef->kseg_ssiz == ctKSEG_SSIZ_COMPUTED
pkdef->kseg_styp == ctKSEG_STYP_PROVIDED
or
pkdef->kseg_ssiz == ctKSEG_SSIZ_COMPUTED
pkdef->kseg_styp == ctKSEG_STYP_UTF8.
The ITIM_ERR persisted after rebuilding the index.
Logic has been corrected to eliminate this error.
Note: It is possible that error 160 will occur on a file where it previously did not appear because the key formation has been changed. Error 160 may be seen on Unicode key segments that are using CT_FSTRING or CT_FUNICODE without null terminators. A rebuild should solve these occurrences.
