Re: [sqlite] large db performance considerations

2009-06-08 Thread Paul Perry
Hi Simon, Thanks for your response. > You need an index, obviously. You can't have an index on a VIRTUAL > table. Yes, I did try on a regular table (not FTS3) and added the indices I described (one each on Author, Content and Category) and still did not notice any performance improvement.

Re: [sqlite] large db performance considerations

2009-06-08 Thread Simon Slavin
On 8 Jun 2009, at 4:45am, Paul Perry wrote: > The latest content I have added, has over 31,000 records. A basic > select, > such as: > > Select Content from BookContent where DocumentID = 10; > takes nearly 15 seconds. Are there any ways to optimize this? You need an index, obviously. You

[sqlite] large db performance considerations

2009-06-07 Thread Paul Perry
Hello, I was wondering if anybody has a tip for optimizing the query time on a table. I have read several web pages about optimizing SQLite queries, but have not been able to come to any conclusions. I have a table: CREATE VIRTUAL TABLE BookContent using fts3( DocumentID INTEGER PRIMARY KEY,