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
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
-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
I'm setting SQLite logging a warning
Warning 0x11C: automatic index on PackageIdByAll(_PackageID)
Whenever I run this SQL
WITH
PackageIdByUser(_PackageID) AS (
SELECT _PackageID FROM Package AS p
INNER JOIN PackageUser AS pu ON pu.Package=p._PackageID
WHERE pu.User=?1 AND
4 matches
Mail list logo