In the meantime, I have found that restricting usable constraints to the fields
present in the selected virtual index nearly restores the orginal query plan.
Field c is now handled by SQlite at the outer level instead of in the query
issued to member tables, forcing more records to be processed
Hello Simon,
Thanks for looking into my issue.
>> If, during your testing, you're using existing database files, please
>> create new ones each time.
I am not sure if I understood this suggestion. After making my code changes, I
creates a new database file in WAL mode and still observed the
SQLite Users,
I'm experiencing unexpected behavior in trying to use the `-pagecache`
option for the `sqlite3` shell. Specifically, the `-pagecache` option
appears to have no effect even though `pragma cache_size` does. I can
see in the code that `-pagecache` causes an allocation which is
3 matches
Mail list logo