On 19 Sep 2009, at 12:55am, Igor Tandetnik wrote:
> Using ICU extension does require certain discipline. You must run
> icu_load_collation soon after opening the database, and all users of
> the
> database must agree to map the same identifiers to the same locales
> (the
> best way to achieve that is probably to make collation name the same
> as
> locale name: SELECT icu_load_collation('he_IL', 'he_IL'); ). Mapping
> the same collation identifier to different locales may indeed result
> in
> corrupted indexes.
>
> For more details, see
> http://www.sqlite.org/cvstrac/fileview?f=sqlite/ext/icu/README.txt
Thanks to you and Jay for explanations. I hadn't encountered ICU at
all before. Your descriptions make perfect sense and are very
interesting since ICU is a good attempt to get around one of the
fundamental problems of Unicode.
Simon.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
