On Tue, May 13, 2014 at 6:50 PM, Jan Slodicka <j...@resco.net> wrote:
> Any comments are welcome. ​This is very interesting Jan. The only way this could fail is if the collation implementation does something funny if it encounters this character​, e.g. choose to ignore it when comparing. Since most collations end up calling the OS unicode API, and this handles U+10FFFD correctly, this should be a very rare case. This may be a reason for Dr Hipp to reject adding this to the LIKE optimization, but anyone could choose to make the optimization manually using BETWEEN instead of LIKE if they are sure that any custom collations they have coded and are using handle U+10FFFD correctly. This is obviously true in your case. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
