Hallo Michael! Zitat aus der FAQ(18) von sqlite.org: Q: Case-insensitive matching of Unicode characters does not work.
A: The default configuration of SQLite only supports case-insensitive comparisons of ASCII characters. The reason for this is that doing full unicode case-insensitive comparisons and case conversions requires tables and logic that would nearly double the size of the SQLite library. The SQLite developers reason that any application that needs full unicode case support probably already has the necessary tables and functions and so SQLite should not take up space to duplicate this ability. Instead of providing full unicode case support by default, SQLite provides the ability to link against external unicode comparison and conversion routines. The application can overload the built-in NOCASE<http://www.sqlite.org/datatype3.html#collation> collating sequence (using sqlite3_create_collation()<http://www.sqlite.org/c3ref/create_collation.html>) and the built-in like() <http://www.sqlite.org/lang_corefunc.html#like>, upper() <http://www.sqlite.org/lang_corefunc.html#upper>, andlower()<http://www.sqlite.org/lang_corefunc.html#lower> functions (using sqlite3_create_function()<http://www.sqlite.org/c3ref/create_function.html>). The SQLite source code includes an "ICU" extension that does these overloads. Or, developers can write their own overloads based on their own unicode-aware comparison routines already contained within their project. Sieht wohl schlecht aus - mit SQLite. Viele Grüße Nicolai
_______________________________________________ rubyonrails-ug mailing list [email protected] http://mailman.headflash.com/listinfo/rubyonrails-ug
