Re: [sqlite] Minor typo in SQLite documentation

Fixed. Thanks. On 6/6/17, Leon Höpfl wrote: > Hello guys, > First of all, thanks for your great work, I really appreciate working > with SQLite. I've recently found a minor typo in > https://sqlite.org/fileformat2.html#sqlite_stat2 in the last row, where > it states "it is exists, is simply igno

[sqlite] Minor typo in SQLite documentation

Hello guys, First of all, thanks for your great work, I really appreciate working with SQLite. I've recently found a minor typo in https://sqlite.org/fileformat2.html#sqlite_stat2 in the last row, where it states "it is exists, is simply ignored", maybe it should state "if it exists, is simply igno

Re: [sqlite] Minor typo in example

On 10/14/16, David Raymond wrote: > In the Row Values page http://www.sqlite.org/rowvalue.html, section 2.2 > there’s an extra semicolon in the code box, turning it into 2 statements. > > > UPDATE tab3 >SET (a,b,c) = (SELECT x,y,z > FROM tab4 >WHERE tab4

Re: [sqlite] Minor typo in example

Two more in here: or an ISO-8601 dates string. But some application store dates On Friday, October 14, 2016 12:27 PM, Robert Weiss wrote: While we're on the subject there are at least two grammatical errors on the same page: there is no substitutions  and A NULL means of "unknown"

Re: [sqlite] Minor typo in example

While we're on the subject there are at least two grammatical errors on the same page: there is no substitutions  and A NULL means of "unknown" On Friday, October 14, 2016 12:20 PM, David Raymond wrote: In the Row Values page http://www.sqlite.org/rowvalue.html, section 2.2 there’s

[sqlite] Minor typo in example

In the Row Values page http://www.sqlite.org/rowvalue.html, section 2.2 there’s an extra semicolon in the code box, turning it into 2 statements. UPDATE tab3 SET (a,b,c) = (SELECT x,y,z FROM tab4 WHERE tab4.w=tab3.d); WHERE tab3.e BETWEEN 55 AND 66;

Re: [sqlite] minor typo in documentation

On Sat, Dec 14, 2013 at 7:00 AM, Kevin Benson wrote: > http://sqlite.org/faq.html#q1 > > CURRENTLY: > "(If the largest possible integer key, 9223372036854775807, then an unused > key value is chosen at random.)" > > SUGGESTED FIX: > " (If the largest possible integer key 9223372036854775807 is in

Re: [sqlite] minor typo in documentation

http://sqlite.org/faq.html#q1 CURRENTLY: "(If the largest possible integer key, 9223372036854775807, then an unused key value is chosen at random.)" SUGGESTED FIX: " (If the largest possible integer key 9223372036854775807 is in use, then an unused key value is chosen at random.)" http://www.s

Re: [sqlite] minor typo in documentation - missing "is"

Thanks. http://www.sqlite.org/docsrc/info/200941601a On Wed, Dec 11, 2013 at 1:23 PM, Jeff Widman wrote: > https://www.sqlite.org/queryplanner.html > > Current: *Then in general the cost of doing the query proportional to > (K+1)*logN.* > > Suggested fix: *Then in general the cost of doing the

[sqlite] minor typo in documentation - missing "is"

https://www.sqlite.org/queryplanner.html Current: *Then in general the cost of doing the query proportional to (K+1)*logN.* Suggested fix: *Then in general the cost of doing the query is proportional to (K+1)*logN.* -- Jeff Widman 740-WIDMAN-J (943-6265) http://www.jeffwidman.com/

[sqlite] Minor typo in release notes

Hi, In http://www.sqlite.org/changes.html , the last change is noted as 2012-04-12 (3.7.16.2). It should probably be 2013 :) Regards, Cédric Cédric VENET Software Engineer - Schlumberger, MpTC Email: cve...@slb.com Tel: +33 4 30 63 85 18 _

[sqlite] minor typo

In the comments at the head of pager.c, there is this: ** The page cache comes up in PAGER_UNLOCK. The first time a ** sqlite3pager_get() occurs, the state transitions to PAGER_SHARED. ** After all pages have been released using sqlite_page_unref(), ** the state transitions back to PAGER_UNLOCK.