it looks like fts1/2 return an ascii string in disguise of a unicode string after an update to the data.
John Stanton wrote: > > In that case your problem will be in your code, specifically in the > function which gives you a pointer to the data. > > Show us your code. > > ohadp wrote: >> i'm linking with it and calling the api directly. >> i think that sqlite3.exe doesn't have fts1 support in it. >> >> >> John Stanton wrote: >> >>>How are you calling Sqlite? Have you tried sqlite3.exe? >>> >>>ohadp wrote: >>> >>>>Scott Hess <[EMAIL PROTECTED]> writes: >>>> >>>> >>>> >>>> >>>>> CREATE VIRTUAL TABLE t USING fts1(content); >>>>> INSERT INTO t (rowid, content) VALUES (1, 'this is a test'); >>>>> UPDATE t SET content = 'that was a test' WHERE rowid = 1; >>>>> >>>>> -- The following is returning 'gibberish here' for me: >>>>> SELECT content FROM t WHERE rowid = 1; >>>>> >>>> >>>> >>>>Hi Scott, >>>> >>>>I'm using the latest version available for download on the sqlite site, >>>>3.3.10. >>>>Compiling on Windows with MSVC (2003). >>>>I tried the script you provide and I get gibberish. >>>>To be sure I selected the data before the update and it comes back >>>>correctly. >>> >>> >>>----------------------------------------------------------------------------- >>>To unsubscribe, send email to [EMAIL PROTECTED] >>>----------------------------------------------------------------------------- >>> >>> >>> >> >> > > > ----------------------------------------------------------------------------- > To unsubscribe, send email to [EMAIL PROTECTED] > ----------------------------------------------------------------------------- > > > -- View this message in context: http://www.nabble.com/3.3.10-data-corruption-on-updating-fts1-string-table-tf2960926.html#a8300239 Sent from the SQLite mailing list archive at Nabble.com. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
