]> git.ipfire.org Git - thirdparty/sqlite.git/commit
http://www.sqlite.org/cvstrac/tktview?tn=2166,35
authorshess <shess@noemail.net>
Fri, 19 Jan 2007 22:59:56 +0000 (22:59 +0000)
committershess <shess@noemail.net>
Fri, 19 Jan 2007 22:59:56 +0000 (22:59 +0000)
commit3ad202dd17200cc6c993ff16569139dd8eb4e07b
treeede24db29a45f05fa073bb295db60c3cb16e6ee7
parentc49de5d98c035e8c5a26dd462fe1730db4367322
http://www.sqlite.org/cvstrac/tktview?tn=2166,35

Calling UPDATE against an fts table in a UTF-16 database inserts
corrupted data into the database.  The UTF-8 data is being inserted
directly.  This appears to happen because sqlite3_ value_text()
destructively coerces a value to UTF-8, and it's never converted back
when updating the table. This works around the problem by rearranging
things so that the update happens before the coercion. (CVS 3596)

FossilOrigin-Name: 4f2ab4b6320ffc621900049b41f50bc30d76d7f5
ext/fts1/fts1.c
ext/fts2/fts2.c
manifest
manifest.uuid
test/fts1i.test [new file with mode: 0644]
test/fts2i.test [new file with mode: 0644]