On 26/4/62 23:56, Jose Isaias Cabrera wrote:
this query. If you try ".expert -verbose", it will tell you the other
This is the output from --verbose
sqlite> .expert --verbose
sqlite> SELECT a.*,sum(b.AnnualDossier) as Dossier FROM Project_List AS a
...> LEFT JOIN Project_ABT_Budget AS b
Dan Kennedy, on Friday, April 26, 2019 12:13 PM wrote...
>On 26/4/62 21:30, Jose Isaias Cabrera wrote:
>Hey! Somebody tried it out! Thanks! :)
I have been using it for a while. ;-) I have been adding INDEXes for queries
used a lot...
>this query. If you try ".expert -verbose", it will tell you
On 26/4/62 21:30, Jose Isaias Cabrera wrote:
Greetings.
sqlite> .expert
sqlite> SELECT a.*,sum(b.AnnualDossier) as Dossier FROM Project_List AS a
...> LEFT JOIN Project_ABT_Budget AS b ON a.ProjID = b.ProjID
...> AND
...> b.InsertDate =
...> (SELECT MAX(InsertDate) FROM
Simon Slavin on Friday, April 26, 2019 10:50 AM wrote...
>On 26 Apr 2019, at 3:30pm, Jose Isaias Cabrera wrote:
>Once you have defined those indices, execute the ANALZE command, then try
>the .expert again.
Thanks.
>What led to you using WHERE 1=1 ? An apparent bug ?
Long story. The app has
On 26 Apr 2019, at 3:30pm, Jose Isaias Cabrera wrote:
> -- On line 5 of the resulted output ,
>
> SCAN TABLE Project_List USING COVERING INDEX Project_Name
>
> Why is it scanning the table using that INDEX if there is no "Project_Name"
> referenced in the query? That is one of the fields of
Greetings.
I want to search the DB for all projects owned by "jic" and I have queried the
DB with the following:
SQLite version 3.28.0 2019-04-16 19:49:53
Enter ".help" for usage hints.
sqlite> .expert
sqlite> SELECT a.*,sum(b.AnnualDossier) as Dossier FROM Project_List AS a
...> LEFT JOIN
6 matches
Mail list logo
