I can send whatever required else if the following bits are not enough.
*The output of .fullschema command:----* sqlite> .fullschema -indent CREATE TABLE 'CLIPPED_UPDATE'( 'name' TEXT, 'edition' INTEGER NOT NULL, 'coverage_id' INTEGER NOT NULL, 'update_no' INTEGER NOT NULL, 'data' BLOB NOT NULL ); CREATE TABLE 'DATASET'( 'name' TEXT NOT NULL, 'edition' INTEGER NOT NULL, 'lcdate' TEXT NOT NULL ); CREATE TABLE 'EXSET'( 'id' INTEGER NOT NULL, 'name' TEXT NOT NULL, 'issue' INTEGER NOT NULL, PRIMARY KEY(id) ); CREATE TABLE 'EXSET_DATASET'( 'exset_id' INTEGER NOT NULL, 'name' TEXT NOT NULL, 'edition' INTEGER NOT NULL, 'chart_code' TEXT NOT NULL, 'update_no' INTEGER NOT NULL, 'coverage_id' INTEGER NOT NULL ); /* No STAT tables available */ ---- *The SQL statement:* ---- SELECT cu.name name, cu.edition edition, cu.update_no update_no, t.pos pos, cu.data data FROM CLIPPED_UPDATE cu INNER JOIN temp.trtu t ON cu.name=t.name AND cu.edition=t.edition INNER JOIN EXSET_DATASET ed ON ed.name=t.name AND ed.edition=t.edition AND ed.coverage_id=cu.coverage_id WHERE ed.exset_id=%d AND cu.update_no>t.update_no ORDER BY name, edition, update_no ---- where %d is some integer (substituted before passing this string to sqlite3_prepare_v2() function), and temp.trtu table is a temp table, created with statement "CREATE TEMP TABLE temp.trtu (name TEXT, edition INTEGER, update_no INTEGER, pos INTEGER) " dixi On 11 August 2016 at 11:48, Richard Hipp <d...@sqlite.org> wrote: > On 8/10/16, Raja Kajiev <raja.kaj...@gmail.com> wrote: > > The issue is: one of requests performed in my app was executed in ~7 > > seconds in v.3.10, but in v.3.14 execution time is ~13-15 seconds. That's > > really itching in my case. > > The sql request in question includes "inner join" constructs. > > I also remember that in version prior to 3.10 the execution time for that > > particular request was much larger than 10 seconds. > > The full code of the routine is below. I can put on share somewhere a > copy > > of the db which is used (it is not a secret data, but it is a little > large > > - about 290 MB). > > Please send: > > (1) The output of the ".fullschema -indent" command as run from the > command-line shell. > (2) The text of the SQL statement that is running slowly. > > -- > D. Richard Hipp > d...@sqlite.org > -- LinkedIn: http://www.linkedin.com/pub/aleksey-smirnov/13/598/3b3 _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
