Re: [sqlite] performance issue, v.3.10 compared to v.3.14 (inner joins)

On 8/16/16, Raja Kajiev wrote: > > *The output of .fullschema command:* > sqlite> .fullschema -indent > CREATE TABLE 'CLIPPED_UPDATE'( > CREATE TABLE 'DATASET'( > CREATE TABLE 'EXSET'( > CREATE TABLE 'EXSET_DATASET'( > /* No STAT tables available */ No indexes. No PRIMARY KEYs. I wonder if

Re: [sqlite] performance issue, v.3.10 compared to v.3.14 (inner joins)

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

Re: [sqlite] performance issue, v.3.10 compared to v.3.14 (inner joins)

On 8/10/16, Raja Kajiev 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 v

[sqlite] performance issue, v.3.10 compared to v.3.14 (inner joins)

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 fo