Simply storing Unicode data has always been possible with c-treeDB API, provided the application treated the data as binary and performed any necessary translations. In this case, using the stored Unicode data as a segment of an index was difficult since c-treeDB API had no way of knowing how the underlying binary data was encoded: UTF-8. UTF-16, ASCII, etc.