On 03/19/2014 05:32 PM, Dan Kennedy wrote:
home-grown tokenizer named "unicode61" that folds case in the same unicode-aware way as nunicode. If the unicode standard changes to define more pairs of case equivalent characters, we will not be able simply upgrade "unicode61". For the same reasons - modifying the comparison function creates an incompatible system. Instead, we would name it "unicode62" or similar, to be sure that databases created using the old version continue to use it.
Thank you for the detailed answer. Is assume working this around with custom collation as in "SELECT ... x = 'ё' COLLATE NOCASE_U61" will imply performance penalty regarding index search, but custom case-insensitive collation assigned to table column, "CREATE TABLE test (x COLLATE NOCASE_U61)", will work as expected.
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
