Re: [sqlite] 0x11C: automatic index warning for CTEs ?

2017-04-25 Thread Clemens Ladisch
Howard Kapustein wrote: >> you might have to change the query itself > > The question is how? The database has estimated that even with the cost of creating the temporary index, this way is the fastest. So it's unlikely that there is another way that would be an improvement. Anyway, try using

Re: [sqlite] 0x11C: automatic index warning for CTEs ?

2017-04-24 Thread Keith Medcalf
t > Subject: Re: [sqlite] 0x11C: automatic index warning for CTEs ? > > >but for CTEs/views/subqueries, you might have to change the query itself, > or the database schema, or determine that the automatic index is the best > choice in your situation. > > Yes. The questio

Re: [sqlite] 0x11C: automatic index warning for CTEs ?

2017-04-24 Thread Howard Kapustein
-Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Clemens Ladisch Sent: Friday, April 21, 2017 11:13 PM To: sqlite-users@mailinglists.sqlite.org Subject: Re: [sqlite] 0x11C: automatic index warning for CTEs ? Howard Kapustein wrote: > I'm se