Re: [sqlite] Performance issue with JOIN and large IN operator

2013-05-01 Thread Richard Hipp
On Wed, May 1, 2013 at 2:11 PM, jic wrote: > "Richard Hipp" wrote... > > Dr. Hipp, > > will this fix break the work-around you provided, > > " > to put a "+" sign in front of the "elements.id" identifier in the ON > clause: > > SELECT count(*) FROM elements JOIN tags ON

Re: [sqlite] Performance issue with JOIN and large IN operator

2013-05-01 Thread jic
"Richard Hipp" wrote... On Wed, May 1, 2013 at 11:24 AM, Richard Hipp wrote: On Wed, May 1, 2013 at 8:30 AM, Martin Altmayer < martin.altma...@googlemail.com> wrote: Hi, I have a query that runs more than 400x slower in 3.7.16.2 than in 3.7.11. This seems to be

Re: [sqlite] Performance issue with JOIN and large IN operator

2013-05-01 Thread Richard Hipp
On Wed, May 1, 2013 at 11:24 AM, Richard Hipp wrote: > > > On Wed, May 1, 2013 at 8:30 AM, Martin Altmayer < > martin.altma...@googlemail.com> wrote: > >> Hi, >> >> I have a query that runs more than 400x slower in 3.7.16.2 than in 3.7.11. >> > > This seems to be caused by the

Re: [sqlite] Performance issue with JOIN and large IN operator

2013-05-01 Thread Richard Hipp
On Wed, May 1, 2013 at 8:30 AM, Martin Altmayer < martin.altma...@googlemail.com> wrote: > Hi, > > I have a query that runs more than 400x slower in 3.7.16.2 than in 3.7.11. > This seems to be caused by the use of transitive constraints in version 3.7.16. Your work-around (until an official fix

[sqlite] Performance issue with JOIN and large IN operator

2013-05-01 Thread Martin Altmayer
Hi, I have a query that runs more than 400x slower in 3.7.16.2 than in 3.7.11. Instead of posting the original query, I post a simplified version which still experiences the problem with a factor of over 100x: SELECT COUNT(*) FROM elements JOIN tags ON elements.id = tags.element_id WHERE