On 25 Jan 2012, at 1:01pm, Igor Tandetnik wrote: > So your query devolves to a full table scan, and apparently, that just takes > a long time.
That's my guess: the query is taking a long time. It's taking long enough that your database infrastructure (which seems to be SQLite Database Browser 2.0) thinks that the SQLite element has crashed and returns an error message. You may be able to find a 'time before error' setting somewhere but Igor's analysis looks like a good starting-point to creating indices or changing the phrasing of your search so it executes in a reasonable time. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
