Hi Clemens, I really appreciate your input but non of your origination have anything to do with the problem at hand. I just want to make sure this thread not get deflected.
The problem is ?performance?. 34157ms, 47924ms vs. 103ms >>SQLite ignores pretty much anything except the column names All right then, it should not influence the performance either. >>You should drop the ID column, and in your queries use the docid instead. Not possible. I fill the rows in a parallel loop, the IDs are in disorder and they are the link to table ?ART.ID?. And even if I would do and let say get a better timing the problem(perhaps bug) would still exist. I am not asking for a solution to my problem. I have it already. - By using ?NOT IN? - I am asking for an acknowledgment that it is a bug or an explanation if it is not. KR, Marta -----Original Message----- From: Clemens Ladisch Sent: Saturday, May 23, 2015 1:29 PM To: sqlite-users at mailinglists.sqlite.org Subject: Re: [sqlite] NOT EXISTS and LEFT JOIN Performance problem ShadowMarta at yahoo.de wrote: > CREATE VIRTUAL TABLE `OCR` using fts4 ( > `ID` integer primary key NOT NULL, This is not how FTS tables work. SQLite ignores pretty much anything except the column names; it does not matter whether you write PRIMARY KEY or NO KEY PLEASE. All columns get full-text indexed. All FTS tables have the usual internal rowid as primary key; it's also available under the name "docid". You should drop the ID column, and in your queries use the docid instead. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
