Hello,
what I describe below probably can't be called a SQLite bug, but in my opinion it could be fixed in SQLite anyway. The problem happens on Windows platform when using Sqlite3_Prepare16(), i.e. function accepting Unicode strings in UTF-16 encoding. When I for example perform a query: SELECT * FROM Table1 Where Field1='XY' where instead of X is 0xD800 Unicode (UTF-16) character, the query fails. It's apparently because 0xD800 is one of UTF-16 surrogates, i.e. the next character is expected to be something like 0xDD00, which isn't our case. What I would propose is to be more robust in handling such incorrect Unicode strings, so that application can e.g. insert really any string, not only those that comply Unicode standards. Thanks, Jiri
