Thanks Simon, >>Only the content you need to search quickly needs to be in an FTS table.
I have only one column with the full text OCR extracted from PDF files and it is what need to be searched. I can't go lower than 1 column its obvious. The "MATCH" gives me back the correct docid which corresponds to the ID in an other table (ART.ID). There must be a way to connect this 2 IDs if not with "JOIN" than how ? Can't believe it isn't possible. KR, Marta -----Original Message----- From: Simon Slavin Sent: Monday, May 25, 2015 3:17 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] NOT EXISTS and LEFT JOIN Performance problem On 25 May 2015, at 2:09pm, ShadowMarta at yahoo.de wrote: > What am I missing here ? My guess is that you are expecting FTS tables to act the same as normal tables. They don't. They're specially created and don't have the same indexing and other behaviour. The questions you're asking make sense if you're just talking about normal SQLite tables. It may be that you should split your data up. For most of your relations you should be declaring normal tables. Only the content you need to search quickly needs to be in an FTS table. Simon. _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
