[sqlite] Documentation error

The page https://sqlite.org/src/doc/begin-concurrent/doc/begin_concurrent.md contains raw html: INSERT INTO t1(b) VALUES(blob-value>); -- Mark Lawrence ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

[sqlite] Documentation error in comment in carray.c

There's a mistake in the documentation block-comment at the start of carray.c: **sqlite3_bind_value(pStmt, i, aX, "carray", 0); The function should be sqlite3_bind_pointer. —Jens ___ sqlite-users mailing list

[sqlite] Documentation error: USE_ZLIB versus HAVE_ZLIB

Good morning! Both https://sqlite.org/cli.html#_do_it_yourself_builds_ and https://sqlite.org/compile.html#use_zlib mention option SQLITE_USE_ZLIB to enable _zipfile and _sqlar. However, shell.c.in uses SQLITE_HAVE_ZLIB for this. I think this is a documentation error. checkout:

Re: [sqlite] Documentation error

On 1/2/19, Joe Jacobs wrote: > > Long story short is that this may be i'm using an old version of sqlite > lite and the command has changed. > Yes. Since 2013-05-20, there have been 73 releases and 10167 distinct changes. One of those 10167 changes was this:

[sqlite] Documentation error

I think this is an error in the command line documentation or room for minor improvement. I was reading through the docs trying to learn about the command line tool and ran into a snag, so i thought i'd report it. https://www.sqlite.org/cli.html In section 3 where it talks about dot commands

Re: [sqlite] Documentation Error

https://www.sqlite.org/c3ref/open.html On Wed, Aug 23, 2017 at 10:29 PM, J Decker wrote: > > > If URI filename interpretation is > enabled, and the filename argument begins with "file:", then the filename > is interpreted as a URI. URI

[sqlite] Documentation Error

If URI filename interpretation is enabled, and the filename argument begins with "file:", then the filename is interpreted as a URI. URI filename interpretation is enabled if the SQLITE_OPEN_URI flag is set in

Re: [sqlite] Documentation error

On 2/15/17, Paul Sanderson wrote: > The process for calculating a checksum text on the SQLite file format page > contains two errors. > Thanks for spotting this. Should be fixed now. -- D. Richard Hipp d...@sqlite.org

[sqlite] Documentation error

The process for calculating a checksum text on the SQLite file format page contains two errors. Currently reads: The checksum is an unsigned 32-bit integer computed as follows: 1. Initialize the checksum to the checksum nonce value found in the journal header at offset 12. 2.

[sqlite] Documentation error in async_cond_wait

This sentence in .../ext/async/sqlite3async.c for async_cond_wait() ** It is guaranteed that no other thread will call async_cond_wait() when ** there is already a thread waiting on the condition variable. is wrong for both Win32 and POSIX implementations. It should be left out or read

[sqlite] Documentation Error: sqlite3_set_authorizer() interface

The documentation is correct after all. The table name is not in the 4th parameter, but in the 6th parameter. The content of the 6th parameter is covered by "The 6th parameter to the authorizer callback is the name of the inner-most trigger or view that is responsible for the access

[sqlite] Documentation Error: sqlite3_set_authorizer() interface

Hello ! Also there is no way to link the callback to specific statement, I think that an extra parameter with the whole sql statement would be needed and/or any other way to link several calls to a statement. Maybe something like: int sqlite3_set_authorizer(sqlite3*,int

[sqlite] Documentation Error: sqlite3_set_authorizer() interface

According to the documentations of The Authorizer Action Codes (http://www.sqlite.org/c3ref/c_alter_table.html): Authorizer Action Codes /*** 3rd 4th ***/ #define SQLITE_SELECT 21 /* NULLNULL

[sqlite] Documentation error: sqlite3_mutex_try

The documentation says that sqlite3_mutex_try will always return SQLITE_BUSY for "some systems (for example, Windows 95)". That's not quite accurate from what I see in the latest implementation of winMutexTry. It will ALWAYS return SQLITE_BUSY for any Windows usage, making the existence of

[sqlite] Documentation error was Re: date field with default current date

http://www.sqlite.org/lang_datefunc.html This page has an error in documenting the range of values when using modifier 'unixepoch'. It says the limit is 10675199167. There should be one more digit in that to get the documented year 5352 result. --David Garfield Mihai Militaru writes: > On

Re: [sqlite] Documentation error in explanation of "IN subquery" (lang_expr.html)

On 14 Jul 2010, at 7:22pm, Richard Hipp wrote: > On Wed, Jul 14, 2010 at 1:25 PM, Simon Slavin wrote: > >> By the way, can someone explain why this rule, equivalent to line 4 of the >> table, is there: >> >> elseif the right op contains NULL, then IN = NULL > >

Re: [sqlite] Documentation error in explanation of "IN subquery" (lang_expr.html)

On Wed, Jul 14, 2010 at 1:25 PM, Simon Slavin wrote: > By the way, can someone explain why this rule, equivalent to line 4 of the > table, is there: > > elseif the right op contains NULL, then IN = NULL > > By the time we've got there we already know that the left

Re: [sqlite] Documentation error in explanation of "IN subquery" (lang_expr.html)

On Jul 15, 2010, at 12:25 AM, Simon Slavin wrote: > > On 14 Jul 2010, at 5:13pm, Richard Hipp wrote: > >> Improvements to the IN operator documentation can be found here: >> >>http://www.sqlite.org/draft/lang_expr.html#in_op > > I find that table difficult to understand: you have some

Re: [sqlite] Documentation error in explanation of "IN subquery" (lang_expr.html)

On 14 Jul 2010, at 5:13pm, Richard Hipp wrote: > Improvements to the IN operator documentation can be found here: > > http://www.sqlite.org/draft/lang_expr.html#in_op I find that table difficult to understand: you have some mutually exclusive columns. Could it be replaced by this

Re: [sqlite] Documentation error in explanation of "IN subquery" (lang_expr.html)

On Wed, Jul 14, 2010 at 8:17 AM, Igor Sereda wrote: > > On page http://www.sqlite.org/lang_expr.html : > > "When a SELECT is the right operand of the IN operator, the IN operator > returns TRUE if the SELECT result contains no NULLs and if the left operand > matches any of the

[sqlite] Documentation error in explanation of "IN subquery" (lang_expr.html)

On page http://www.sqlite.org/lang_expr.html : "When a SELECT is the right operand of the IN operator, the IN operator returns TRUE if the SELECT result contains no NULLs and if the left operand matches any of the values in the SELECT result." The part "SELECT result contains no NULLs" does not