Re: [sqlite] Tiny typo in doc.

On 5/22/17, Donald Griggs wrote: > http://www.sqlite.org/releaselog/3_19_0.html > > "containing two ore more" > Thank you. And since "ore" is a real word, the spelling checker didn't catch this. :-\ -- D. Richard Hipp d...@sqlite.org

[sqlite] Tiny typo in doc.

http://www.sqlite.org/releaselog/3_19_0.html "containing two ore more" Not a complaint, just hoping to be helpful. Donald ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] Tiny typo in doc.

Richard Hipp wrote: > On 5/22/17, Donald Griggs wrote: >> http://www.sqlite.org/releaselog/3_19_0.html >> >> "containing two ore more" >> > > Thank you. And since "ore" is a real word, the spelling checker > didn't catch this. :-\ Another typo not caught by the

[sqlite] Sqlite3 CLI enhancement request

While checking something else I came across this. SQLite version 3.16.0 2016-11-04 19:09:39 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> PRAGMA foreign_keys = ON; sqlite> PRAGMA foreign_keys; 1 sqlite>

Re: [sqlite] Thank you for your work

Am Fri, 19 May 2017 13:36:57 -0400 schrieb Richard Hipp: > On 5/19/17, Claudio Bantaloukas wrote: >> >> Lo and behold, the latest version handled these queries without issue, >> halved the time it took to run some other queries and has apparently not >> introduced

[sqlite] Minor issue: compile error with 3.19 and MSVC 2005

Hallo, I don't think this is a big deal, but probably helpful for one or another: I tried to compile SQLite 3.19 with MSVC 2005 and got a compile error C2143 at line 143542 of sqlite3.c. Removing the trailing semicolon from if( (zKey = sqlite3_uri_parameter(zOpen, "hexkey"))!=0 && zKey[0] ){;

Re: [sqlite] vtable and usable constraint

Gunter. Thank you very much for the insightful and detailed answer. May I ask the obvious and possibly oversimplified question? This is directed to anyone especially those privy to the worked VTab examples DRH mentioned. Suppose the virtual table is merely a light wrapper over backing_table.

Re: [sqlite] vtable and usable constraint

SQLite will determine the set of constraints that are possible against yout virtual table from the query you are preparing. It will then call your xBestIndex function a number of times with different subsets of the constraints marked aus "usable". Your xBestIndex function needs to return (among

[sqlite] SQLDiff.exe and sqlite3changeset_apply

Hello I have bug releated to SQLDiff and sqlite3changeset_apply: Here is situation: - For testing I have simple database with two tables - I'm running SQLDiff.exe with --changeset option - Next I'm trying apply patch to database by sqlite3changeset_apply If I have changes to booth tables

Re: [sqlite] explain query plan for 'where ID between ...'

xTom Byars wrote: > Returns > > SEARCH TABLE Tbl USING PRIMARY KEY (ID>? AND ID > Should that be (ID>=? AND ID<=?) explain query plan select * from t where x between 1 and 42; 0|0|0|SEARCH TABLE t USING PRIMARY KEY (x>? AND x= 1 and stops with > 42. The EQP output does not bother to always use

Re: [sqlite] SQLDiff.exe and sqlite3changeset_apply

On 05/22/2017 09:49 PM, Green wrote: Hello I have bug releated to SQLDiff and sqlite3changeset_apply: Thanks for reporting this. Now fixed here: http://www.sqlite.org/src/info/0bb23c48064cc641 Dan. Here is situation: - For testing I have simple database with two tables - I'm