On Jul 13, 2016 9:55 AM, "Simon Slavin" <[email protected]> wrote: > > > On 13 Jul 2016, at 4:09pm, S.Ajina <[email protected]> wrote: > > > Doing the same with the current version of sqlite3.exe (version 3.13.0) corrupts the database records when there are extended characters > > I would guess that your program is handing extended characters to SQLite incorrectly. All strings passed to SQLite are assumed to be Unicode strings. This includes not only strings used as parameters when binding to a SQL statement, but also the SQL statements themselves.
His program is not involved. Just the SQLite shell. > > Given the way you phrased your question, I assume you've been using MBCS. > > If you make up a string which depends on a Windows codepage, and do not explicitly convert this string to Unicode before handing it to SQLite, you will get bad results. Maybe not immediately, but later, perhaps after indexing. > > As a test, please execute this command against both versions of the database: > > SELECT path,hex(path) FROM "test-directories" WHERE id=68 > > You (or we) should be able to tell what's happening from the results of that. > > Simon. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
