Index update lookup errors with many nil values in Unicode indexes
When the indexed instance variable is nil in a Unicode String index, the nil values are not sorted correctly. If there are a large number of sequential nils (sufficient to fill a leaf node in the btree), the nil values may not be found. This results in lookup errors when making updates to the index, such as when making changes to elements.
Workaround
File in the following as SystemUser and commit:method: UndefinedObject _idxForSortEqualTo: aCharacterCollection collator: collator ^ self _idxForSortEqualTo: aCharacterCollection %After installing this fix, you need to drop and rebuild the affected indexes. To do this, you will need to remove all indexes on the collection using #removeAllIndexes, since attempting to remove individual indexes would encounter the lookup error.
Last updated: 10/16/14