> > In either case the wrapping and registration with > sqlite_create_collation_v2 > is quite easy. >
Yes, it is. I thought that the actual algorithm would be harder but I was wrong. It's surprisingly ease and simple to build a simple algorithm to handle utf8 ASCII and Latin Basic plane with standard rules. The implementation runs extremely fast comparing to ICU implementation and covers 100% of my use cases. The algorithm is based on original NOCASE from SQLite and it runs near fast. It takes just less than 20 lines of actual C code. This is lite. > Most users actually don't care about the collation sequence, because they > neither order by strings nor use like on strings (or only use them with > identifiers, that fit in ascii anyway). Most of the rest either wants the > collation to be correct in all cases (so they use ICU) or go with the > simplest solution (so they use ICU). The few that don't want ICU just > define > the collation sequences themselves. > > For me the simplest solution it is my own implementation. I thought that someone else had build it some simple and I wouldn't need to reinvent the wheel. Thanks. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users