I now believe that check-in https://www.sqlite.org/src/timeline?c=51027f08c0478f1b is the complete and correct fix for the reported problem with UTF16 surrogate pairs in JSON. I have checked in new test cases (to TH3, where, unfortunately, you cannot see them). If anybody sees anything that I have overlooked, please post a follow-up comment.
Thanks again to Serhiy for bringing the problem to my attention by posting on the mailing list. Serhiy: In case it helps: You can go to the check-in info page (https://www.sqlite.org/src/info/51027f08c0478f1b) and click on the "tarball" link to get a source code tarball, then build the amalgamation for testing using: ./configure && make sqlite3.c -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
