Thanks for your response. https://www.sqlite.org/faq.html#q18
>>The SQLite source code includes an "ICU" extension that does these overloads. Will it solve for all charsets if ICU enabled? On Thu, Oct 23, 2014 at 6:28 PM, Constantine Yannakopoulos < alfasud...@gmail.com> wrote: > On Thu, Oct 23, 2014 at 2:47 PM, dd <durga.d...@gmail.com> wrote: > > > Hi, > > > > database schema defined with collate nocase. It supports only for ascii > > (upper and lower). If I want to support db for other characters with > > nocase, what steps I need to consider during schema design. > > > > for ex: > > > > *À Á Â Ã Ä Å Æ = * > > > > * à á â ã ä å æ * > > > > you can write your own collations > <https://www.sqlite.org/c3ref/create_collation.html> to support custom > comparing and sorting of strings or any other data and add them to SQLite > <https://www.sqlite.org/c3ref/collation_needed.html>. > > There is a pitfall though: The LIKE operator will not honour your > collation > <http://www.sqlite.org/lang_expr.html#like>. You may choose to override it > <http://www.sqlite.org/lang_corefunc.html#like> by using the > sqlite3_create_function() api so that it does, but if you do you will lose > the LIKE optimization <http://www.sqlite.org/optoverview.html#like_opt>. > > -- > Constantine > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
