On Wed, Aug 4, 2010 at 16:30, Scott Hess <sh...@google.com> wrote: > You should probably pull the current SQLite code and make sure the > patch even applies, and if not, check to make sure that the problem > hasn't already been fixed. ext/fts3 should no longer have the flaw in > question, as that code was heavily rewritten.
Yeah, the fts3 parts no longer apply and are not included in the patch sent here. I'm working on the latest (fossil) SQLite codebase. > The fts1/2 changes would probably be better recast in the mode of the > fts3 changes. The relevant comment where things are coming clear was: > http://code.google.com/p/chromium/issues/detail?id=15261#c20 Yes, that would be a good direction. However, I'm not yet very familiar with the SQLite codebase, so I sent something that is in our codebase, doesn't break tests, and asked for suggestions. We could then see how SQLite fixed the problem in fts3, and backport that to Chromium's copy. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
