Hi Richard, On 16.05.2018 12:32, Richard Hipp wrote: >> Actually it is: SQLite will generate the same query plan for both >> queries as long as no statistics data is available. Adding the >> statistics information will lead to the more complex and slow query plan >> which is why I kept the statistics in the example SQL. > > Can you please send the output of ".fullschema" so that I can try to > reproduce your problem?
I sent the steps to reproduce this problem to the list last week. As there was no reaction from you so far I assume that this was enough information? Anyway, should you need more for reproducing this (assuming that you are interested at all) please contact me directly as I do not have the time to regularly read the sqlite-users list. Our application now uses a query that leads to the better query plan so there is no hurry to fix this, I am just curious about what might cause it. Greetings, Torsten -- $---+----1----+----2----+----3----+----4----+----5----+----6----+ SCALE GmbH Niederlassung Dresden Torsten Landschoff Pohlandstraße 19 01309 Dresden Tel: +49-351-312002-10 Fax: +49-351-312002-29 SCALE GmbH Registergericht und Sitz: Ingolstadt, HRB 6384 Geschäftsführer: Dr.-Ing. Heiner Müllerschön, Dipl.-Math. Ulrich Franz _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
