Hello thank you for your prompt answer and fix.
I've jus tested the 3.14 pre-release and now all work right follows the explain query result with 3.14 (OK) explain query plan SELECT ...> pupdate,idinstrum,Vlnsys,Vl1n,Vl2n,Vl3n,Vllsys,Vl1l2,Vl2l3,Vl3l1, ...> Al1,Al2,Al3,kWsys,kWl1,kWl2,kWl3,kWhac, ...> kWhacn,kvarsys,kvarl1,kvarl2,kvarl3,kvarhn,kvarh, ...> kvarhacC,kvarhacL,kVAsys,kVAl1,kVAl2 ,kVAl3,PSeq, ...> THDAl1,THDAl2,THDAl3,THDVl1n,THDVl2n,THDVl3n, ...> kWhl1 ,kWhl2 ,kWhl3 ,counter1,counter2,counter3,Hz,An,Hour,Hourn, ...> Alsys,kvarhl1,kvarhl2,kvarhl3,kvarhnl1,kvarhnl2,kvarhnl3,kWhnl1,kWhnl2, ...> kWhnl3,kVAh,kVAhl1,kVAhl2,kVAhl3, ...> PFsys,PFl1,PFl2,PFl3,Wdmd,vardmd,VAdmd ...> FROM hst_energy_d ...> WHERE enflag = 0 ORDER BY recdate DESC, rectime DESC LIMIT 1; 0|0|0|SCAN TABLE hst_energy_d USING INDEX energy_d_dateTimeIdx follows the explain query result with 3.13 (NOK) explain query plan SELECT ...> pupdate,idinstrum,Vlnsys,Vl1n,Vl2n,Vl3n,Vllsys,Vl1l2,Vl2l3,Vl3l1, ...> Al1,Al2,Al3,kWsys,kWl1,kWl2,kWl3,kWhac, ...> kWhacn,kvarsys,kvarl1,kvarl2,kvarl3,kvarhn,kvarh, ...> kvarhacC,kvarhacL,kVAsys,kVAl1,kVAl2 ,kVAl3,PSeq, ...> THDAl1,THDAl2,THDAl3,THDVl1n,THDVl2n,THDVl3n, ...> kWhl1 ,kWhl2 ,kWhl3 ,counter1,counter2,counter3,Hz,An,Hour,Hourn, ...> Alsys,kvarhl1,kvarhl2,kvarhl3,kvarhnl1,kvarhnl2,kvarhnl3,kWhnl1,kWhnl2, ...> kWhnl3,kVAh,kVAhl1,kVAhl2,kVAhl3, ...> PFsys,PFl1,PFl2,PFl3,Wdmd,vardmd,VAdmd ...> FROM hst_energy_d ...> WHERE enflag = 0 ORDER BY recdate DESC, rectime DESC LIMIT 1; 0|0|0|SCAN TABLE hst_energy_d 0|0|0|USE TEMP B-TREE FOR ORDER BY For me is OK regards Alessandro --------------------------------------------------- Alessandro Fardin Carlo Gavazzi Controls SpA - R&D Via Cima i Prà, 9/H 32014 Ponte Nelle Alpi (BL) - ITALY Phone: (+39)0437.355811 / Fax: (+39)0437.355880 Visit our site: www.gavazziautomation.com e-mail: alessandro.far...@gavazziacbu.it --------------------------------------------------- From: Richard Hipp <d...@sqlite.org> To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Cc: alessandro.far...@gavazziacbu.it Date: 27/07/2016 21:33 Subject: Re: [sqlite] sqlite 3.13.0 does not use indexes as 3.8.11.1 does Sent by: drhsql...@gmail.com On 7/26/16, Alessandro Fardin <alessandro.far...@gavazziacbu.it> wrote: > After updating from sqlite 3.8.11.1 to sqlite 3.13.0. > > The Query planner with the same SELECT statement on same table with the > same indexes does not use index at all, but parse the entire table. > Of course this causes a dramatically slow down of the application. This problem should now be fixed in the latest Prerelease Snapshot available at https://www.sqlite.org/download.html - please confirm that the problem is resolved. We are holding up the release of SQLite version 3.14 waiting on your confirmation. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
