On Oct 12, 2009, at 10:20 PM, Jean-Christophe Deschamps wrote: > > I'm surprised that if I register overloading functions for LIKE or > GLOB > in both UTF-8 and UTF-16, only the UTF-16 version is called despite > the > fact that the database is UTF-8.
I'm surprised by this too. In fact, I cannot reproduce it. > > I don't see the same behavior with the other scalar functions (lower, > upper), which call the UTF-8 version as expected for UTF-8 database. > > Are LIKE & GLOB special in this respect that a separate entry point > registered for UTF-8 input is useless? LIKE and GLOB are the same as other functions. I have added test cases to SQLite verify that correct encoding (UTF8 or UTF16) of overloaded LIKE and GLOB functions are called based on the database encoding. D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
