When I got that error I, for some reason, interpreted it as an SQL-level error message, and not an FTS-level one. Now I realise that it indicates an FTS-level error, so it makes sense. Since I thought it was an SQL-level error I thought it was an SQL injection bug. Sorry for crying wolf.
It would be nice if there was a mode which was more accepting towards FTS query errors for end user authored queries, but now I'm happy when I understand why I got the error and can deal with it appropriately. Cheers, Jonas On Sat, Jan 15, 2011 at 3:11 PM, Richard Hipp <d...@sqlite.org> wrote: > On Fri, Jan 14, 2011 at 8:18 PM, Jonas Bengtsson <jona...@gmail.com> wrote: > >> Hi all, >> >> I've found a defect in FTS3 where it will accept matching with the >> string "" (two quotes) but not """ (three quotes). >> >> Three double-quotes is not a valid query string, so FTS3/4 returns an error > code. > > What are you suggesting it should do? Ignore the error? > > > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
