SQLite User Forum

ERROR: stale evidence at build.c:3712 - R-30323-21917 (SQLite docs)
Login
Chronological

ERROR: stale evidence at build.c:3712 - R-30323-21917 (SQLite docs)

(1) By userABCD on 2024-11-02 11:35:09 [link] [source] 

I get multiple "ERROR: stale evidence at ..." errors when building the doc. I include the full output below. Apparently the docs still build okay, or at least they appear okay when I examine the result, the exit code from "make all" is 0.

I am building completely from scratch, my build script is this:
==================================
# SQLite3 DOCS

# tcl 8.6
tar -xf "${ROOT}"/tcl8.6.14-src.tar.gz || exit 1

# source
if test -e sqliteDoc ; then
        rm -r sqliteDoc/ || exit 1
fi
mkdir -p sqliteDoc || exit 1
pushd sqliteDoc || exit 1
fossil open "${ROOT}"/sqliteDoc.fossil trunk --nosync || exit 1

# modify
sed -i "s;TCLINC =.*;TCLINC = -I${TEMP}/tcl8.6.14/generic;" Makefile || exit 1
sed -i 's;TH3 =.*;TH3 =;' Makefile || exit 1
sed -i 's;SLT =.*;SLT =;' Makefile || exit 1

# make
make all || exit 1
==================================

The full output is this:
==================================
project-name: Documentation Source Text
repository:   [redacted]/sqlite/sqliteDoc.fossil
local-root:   /dev/shm/sqliteDoc/
config-db:    [redacted]/.fossil
project-code: a49a74a282acfe2f07de91768b854dffd3d783df
checkout:     d73ec835ebd862c696a06f21dc4f58f735e4289b 2024-11-01 11:21:37 UTC
parent:       8dc64cf91a3876c70f830c9e70ff9d2b9ab72515 2024-10-24 10:55:33 UTC
tags:         trunk
comment:      Add a change-log entry for 3.48.0. (user: drh)
check-ins:    4572
gcc -g -Wall -I../sqlite -O2 -o tclsh.docsrc -I. -I/dev/shm/tcl8.6.14/generic -DSQLITE_THREADSAFE=0 -DSQLITE_ENABLE_FTS5 -DSQLITE_TCLMD5 -DPIKCHR_TCL -DTCLSH -Dmain=xmain ./search/searchc.c ./search/parsehtml.c ./search/fts5ext.c ./search/pikchr.c ../sqlite/src/test_md5.c ../sqlite/tclsqlite3.c -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lm -lpthread -lz
cp ../sqlite/sqlite3.h ./orig-sqlite3.h
sed 's/^SQLITE_API //' ./orig-sqlite3.h >./sqlite3.h
mkdir -p ./doc ./doc/c3ref ./doc/matrix
mkdir -p ./doc/matrix/c3ref ./doc/matrix/syntax
./tclsh.docsrc ./schema.tcl
rm -rf ./doc/images
cp -r ./images ./doc
cp ./rawpages/* ./doc
./tclsh.docsrc ./wrap.tcl . ../sqlite ./doc ./pages/*.in
Gathering links from 211 input files ....................................
Transforming 211 files to ./doc/*.html ....................................
Preserving collected link data for incremental builds.
Writing 4 link arrays to 'doc_vardump.txt'
Page processing succeeded with no errors.
cp ./doc/fileformat2.html ./doc/fileformat.html
./tclsh.docsrc ./scan_test_cases.tcl -reset src ../sqlite/src/*.[chy]
./tclsh.docsrc ./scan_test_cases.tcl src ../sqlite/ext/fts3/*.[ch]
./tclsh.docsrc ./scan_test_cases.tcl src ../sqlite/ext/rtree/*.h
./tclsh.docsrc ./scan_test_cases.tcl src ../sqlite/ext/rtree/rtree.c
./tclsh.docsrc ./scan_test_cases.tcl src ../sqlite/ext/rtree/geopoly.c
./tclsh.docsrc ./scan_test_cases.tcl tcl ../sqlite/ext/rtree/test_rtreedoc.c
./tclsh.docsrc ./scan_test_cases.tcl tcl ../sqlite/ext/rtree/*.test
./tclsh.docsrc ./scan_test_cases.tcl tcl ../sqlite/test/*.test
if test '' != ''; then \
  ./tclsh.docsrc ./scan_test_cases.tcl th3 /mkth3.tcl; \
  ./tclsh.docsrc ./scan_test_cases.tcl th3 /base/*.c; \
  ./tclsh.docsrc ./scan_test_cases.tcl th3/req1 /req1/*.test; \
  ./tclsh.docsrc ./scan_test_cases.tcl th3/cov1 /cov1/*.test; \
  ./tclsh.docsrc ./scan_test_cases.tcl th3/stress /stress/*.test; \
fi
if test '' != ''; then \
  ./tclsh.docsrc ./scan_test_cases.tcl slt /test/evidence/*.test; \
fi
rm -fr ./doc/matrix/ev/*
./tclsh.docsrc ./format_evidence.tcl src ./doc/matrix ../sqlite/src/*.[chy]
./tclsh.docsrc ./format_evidence.tcl src ./doc/matrix ../sqlite/ext/fts3/*.[ch]
./tclsh.docsrc ./format_evidence.tcl src ./doc/matrix ../sqlite/ext/rtree/*.[ch]
./tclsh.docsrc ./format_evidence.tcl tcl ./doc/matrix ../sqlite/test/*.test
if test '' != ''; then \
  ./tclsh.docsrc ./format_evidence.tcl slt ./doc/matrix /test/evidence/*.test; \
fi
rm -rf ./doc/matrix/images
cp -r ./doc/images ./doc/matrix
cp ./rawpages/sqlite.css ./doc/matrix
./tclsh.docsrc ./matrix.tcl
Scanning documentation for testable statements.............................................................................................................................................................................................................................................................................................................................................lang_transaction.html: duplicate R-03042-35027 in c3ref/sleep.html: [In SQLite version 3.]
.......................................................................................................................................................................
Found 3486 testable statements. Evidence exists for 975 or 28.0%
ERROR: stale evidence at build.c:3712 - R-30323-21917
... in foreignkeys.html: "Each foreign key constraint in SQLite is classified as either immediate or deferred."
ERROR: stale evidence at ctime.c:24 - R-16824-07538
... in c3ref/compileoption_get.html: "Support for the diagnostic functions sqlite3_compileoption_used() and sqlite3_compileoption_get() may be omitted by specifying the SQLITE_OMIT_COMPILEOPTION_DIAGS option at compile time."
ERROR: stale evidence at date.c:741 - R-33611-57934
... in lang_datefunc.html: "The "auto" modifier must immediately follow the initial time-value."
ERROR: stale evidence at date.c:788 - R-31176-64601
... in lang_datefunc.html: "Any other use of the 'julianday' modifier is an error and causes the function to return NULL."
ERROR: stale evidence at date.c:819 - R-49255-55373
ERROR: stale evidence at func.c:1368 - R-00293-64994
... in lang_corefunc.html: "This SQL function is implemented using the sqlite3_result_zeroblob() routine from the C/C++ interface."
ERROR: stale evidence at insert.c:2094 - R-26383-51744
... in lang_conflict.html: "If a CHECK constraint or foreign key constraint violation occurs, the REPLACE conflict resolution algorithm works like ABORT."
ERROR: stale evidence at main.c:447 - R-54466-46756
... in c3ref/c_config_covering_index_scan.html: "If SQLite is compiled with the SQLITE_THREADSAFE=0 compile-time option then it is not possible to change the threading mode from its default value of Single-thread and so sqlite3_config() will return SQLITE_ERROR if called with the SQLITE_CONFIG_SINGLETHREAD configuration option."
ERROR: stale evidence at main.c:456 - R-20520-54086
... in c3ref/c_config_covering_index_scan.html: "If SQLite is compiled with the SQLITE_THREADSAFE=0 compile-time option then it is not possible to set the Multi-thread threading mode and sqlite3_config() will return SQLITE_ERROR if called with the SQLITE_CONFIG_MULTITHREAD configuration option."
ERROR: stale evidence at main.c:465 - R-59593-21810
... in c3ref/c_config_covering_index_scan.html: "If SQLite is compiled with the SQLITE_THREADSAFE=0 compile-time option then it is not possible to set the Serialized threading mode and sqlite3_config() will return SQLITE_ERROR if called with the SQLITE_CONFIG_SERIALIZED configuration option."
ERROR: stale evidence at main.c:474 - R-63666-48755
... in c3ref/c_config_covering_index_scan.html: "If SQLite is compiled with the SQLITE_THREADSAFE=0 compile-time option then the entire mutexing subsystem is omitted from the build and hence calls to sqlite3_config() with the SQLITE_CONFIG_MUTEX configuration option will return SQLITE_ERROR."
ERROR: stale evidence at main.c:481 - R-14450-37597
... in c3ref/c_config_covering_index_scan.html: "If SQLite is compiled with the SQLITE_THREADSAFE=0 compile-time option then the entire mutexing subsystem is omitted from the build and hence calls to sqlite3_config() with the SQLITE_CONFIG_GETMUTEX configuration option will return SQLITE_ERROR."
ERROR: stale evidence at main.c:697 - R-04780-55815
... in c3ref/c_config_covering_index_scan.html: "The SQLITE_CONFIG_WIN32_HEAPSIZE option is only available if SQLite is compiled for Windows with the SQLITE_WIN32_MALLOC pre-processor macro defined."
ERROR: stale evidence at main.c:787 - R-33038-09382
... in c3ref/c_dbconfig_defensive.html: "If the second argument to SQLITE_DBCONFIG_LOOKASIDE is not a multiple of 8, it is internally rounded down to the next smaller multiple of 8."
ERROR: stale evidence at main.c:795 - R-61949-35727
... in c3ref/c_dbconfig_defensive.html: "The first argument after the SQLITE_DBCONFIG_LOOKASIDE verb may be NULL in which case SQLite will allocate the lookaside buffer itself using sqlite3_malloc()."
ERROR: stale evidence at main.c:946 - R-06824-28531
... in c3ref/c_dbconfig_defensive.html: "This option is used to change the name of the "main" database schema."
ERROR: stale evidence at main.c:947 - R-36257-52125
... in c3ref/c_dbconfig_defensive.html: "SQLite does not make a copy of the new main schema name string, so the application must ensure that the argument passed into this DBCONFIG option is unchanged until after the database connection closes."
ERROR: stale evidence at main.c:953 - R-26835-10964
... in c3ref/c_dbconfig_defensive.html: "The first argument (the third parameter to sqlite3_db_config() is a pointer to a memory buffer to use for lookaside memory."
ERROR: stale evidence at main.c:954 - R-47871-25994
... in c3ref/c_dbconfig_defensive.html: "The second argument is the size of each lookaside buffer slot."
ERROR: stale evidence at main.c:955 - R-04460-53386
... in c3ref/c_dbconfig_defensive.html: "The third argument is the number of slots."
ERROR: stale evidence at main.c:985 - R-42790-23372
... in c3ref/c_dbconfig_defensive.html: "The sqlite3_db_config() interface will return a non-zero error code if a discontinued or unsupported configuration option is invoked."
ERROR: stale evidence at main.c:2837 - R-38091-32352
... in lang_expr.html: "The maximum parameter number is set at compile-time by the SQLITE_MAX_VARIABLE_NUMBER macro."
ERROR: stale evidence at main.c:2925 - R-52476-28732
... in c3ref/limit.html: "If the new limit is a negative number, the limit is unchanged."
ERROR: stale evidence at main.c:2927 - R-51463-25634
... in c3ref/limit.html: "Attempts to increase a limit above its hard upper bound are silently truncated to the hard upper bound."
ERROR: stale evidence at main.c:2933 - R-53341-35419
... in c3ref/limit.html: "Regardless of whether or not the limit was changed, the sqlite3_limit() interface returns the prior value of the limit."
ERROR: stale evidence at main.c:2979 - R-48725-32206
... in c3ref/c_config_covering_index_scan.html: "If it is globally disabled, filenames are only interpreted as URIs if the SQLITE_OPEN_URI flag is set when the database connection is opened."
ERROR: stale evidence at main.c:2980 - R-51689-46548
... in c3ref/c_config_covering_index_scan.html: "If URI handling is globally enabled, all filenames passed to sqlite3_open(), sqlite3_open_v2(), sqlite3_open16() or specified as part of ATTACH commands are interpreted as URIs, regardless of whether or not the SQLITE_OPEN_URI flag is set when the database connection is opened."
ERROR: stale evidence at main.c:2981 - R-57884-37496
... in uri.html: "The scheme of the URI must be "file:". Any other scheme results in the input being treated as an ordinary filename."
ERROR: stale evidence at main.c:3446 - R-18321-05872
... in c3ref/open.html: "The flags parameter to sqlite3_open_v2() must include, at a minimum, one of the following three flag combinations:"
ERROR: stale evidence at malloc.c:328 - R-11148-40995
... in c3ref/free.html: "The memory returned by sqlite3_malloc(), sqlite3_realloc(), sqlite3_malloc64(), and sqlite3_realloc64() is always aligned to at least an 8 byte boundary, or to a 4 byte boundary if the SQLITE_4_BYTE_ALIGNED_MALLOC compile-time option is used."
ERROR: stale evidence at malloc.c:413 - R-49053-54554
... in c3ref/free.html: "The sqlite3_free() routine is a no-op if is called with a NULL pointer."
ERROR: stale evidence at malloc.c:530 - R-04300-56712
... in c3ref/free.html: "If the X parameter to sqlite3_realloc(X,N) is a NULL pointer then its behavior is identical to calling sqlite3_malloc(N)."
ERROR: stale evidence at malloc.c:533 - R-26507-47431
... in c3ref/free.html: "If the N parameter to sqlite3_realloc(X,N) is zero or negative then the behavior is exactly the same as calling sqlite3_free(X)."
ERROR: stale evidence at malloc.c:576 - R-11148-40995
... in c3ref/free.html: "The memory returned by sqlite3_malloc(), sqlite3_realloc(), sqlite3_malloc64(), and sqlite3_realloc64() is always aligned to at least an 8 byte boundary, or to a 4 byte boundary if the SQLITE_4_BYTE_ALIGNED_MALLOC compile-time option is used."
ERROR: stale evidence at malloc.c:588 - R-26507-47431
... in c3ref/free.html: "If the N parameter to sqlite3_realloc(X,N) is zero or negative then the behavior is exactly the same as calling sqlite3_free(X)."
ERROR: stale evidence at mem1.c:213 - R-46199-30249
... in c3ref/mem_methods.html: "SQLite guarantees that the second argument to xRealloc is always a value returned by a prior call to xRoundup."
ERROR: stale evidence at mem2.c:347 - R-46199-30249
... in c3ref/mem_methods.html: "SQLite guarantees that the second argument to xRealloc is always a value returned by a prior call to xRoundup."
ERROR: stale evidence at mem5.c:395 - R-46199-30249
... in c3ref/mem_methods.html: "SQLite guarantees that the second argument to xRealloc is always a value returned by a prior call to xRoundup."
ERROR: stale evidence at parse.y:419 - R-19803-45884
... in foreignkeys.html: "If an action is not explicitly specified, it defaults to "NO ACTION"."
ERROR: stale evidence at parse.y:427 - R-33326-45252
... in foreignkeys.html: "The ON DELETE and ON UPDATE action associated with each foreign key in an SQLite database is one of "NO ACTION", "RESTRICT", "SET NULL", "SET DEFAULT" or "CASCADE"."
ERROR: stale evidence at parse.y:428 - R-33326-45252
... in foreignkeys.html: "The ON DELETE and ON UPDATE action associated with each foreign key in an SQLite database is one of "NO ACTION", "RESTRICT", "SET NULL", "SET DEFAULT" or "CASCADE"."
ERROR: stale evidence at parse.y:429 - R-33326-45252
... in foreignkeys.html: "The ON DELETE and ON UPDATE action associated with each foreign key in an SQLite database is one of "NO ACTION", "RESTRICT", "SET NULL", "SET DEFAULT" or "CASCADE"."
ERROR: stale evidence at parse.y:430 - R-33326-45252
... in foreignkeys.html: "The ON DELETE and ON UPDATE action associated with each foreign key in an SQLite database is one of "NO ACTION", "RESTRICT", "SET NULL", "SET DEFAULT" or "CASCADE"."
ERROR: stale evidence at parse.y:431 - R-33326-45252
... in foreignkeys.html: "The ON DELETE and ON UPDATE action associated with each foreign key in an SQLite database is one of "NO ACTION", "RESTRICT", "SET NULL", "SET DEFAULT" or "CASCADE"."
ERROR: stale evidence at pragma.c:2696 - R-40975-20399
... in pragma.html: "If N is a negative number or something other than an integer value, then the pragma behaves as if the N argument was omitted."
ERROR: stale evidence at pragma.c:2701 - R-57594-65522
... in pragma.html: "In all cases, the value returned is the new analysis limit used for subsequent ANALYZE commands."
ERROR: stale evidence at resolve.c:576 - R-51414-32910
... in lang_createtable.html: "Except for WITHOUT ROWID tables, all rows within SQLite tables have a 64-bit signed integer key that uniquely identifies the row within its table."
ERROR: stale evidence at sqliteInt.h:367 - R-07272-22309
... in c3ref/threadsafe.html: "The default behavior is for mutexes to be enabled."
ERROR: stale evidence at sqliteInt.h:2547 - R-30323-21917
... in foreignkeys.html: "Each foreign key constraint in SQLite is classified as either immediate or deferred."
ERROR: stale evidence at status.c:347 - R-64479-57858
... in c3ref/c_dbstatus_options.html: "The highwater mark associated with SQLITE_DBSTATUS_STMT_USED is always 0."
ERROR: stale evidence at status.c:375 - R-42420-56072
... in c3ref/c_dbstatus_options.html: "The highwater mark associated with SQLITE_DBSTATUS_CACHE_HIT is always 0."
ERROR: stale evidence at status.c:376 - R-54100-20147
... in c3ref/c_dbstatus_options.html: "The highwater mark associated with SQLITE_DBSTATUS_CACHE_MISS is always 0."
ERROR: stale evidence at status.c:377 - R-29431-39229
... in c3ref/c_dbstatus_options.html: "The highwater mark associated with SQLITE_DBSTATUS_CACHE_WRITE is always 0."
ERROR: stale evidence at status.c:387 - R-11967-56545
... in c3ref/c_dbstatus_options.html: "The highwater mark is always 0."
ERROR: stale evidence at tokenize.c:291 - R-22934-25134
... in lang_comment.html: "Comments are treated as whitespace by the parser."
ERROR: stale evidence at tokenize.c:327 - R-22934-25134
... in lang_comment.html: "Comments are treated as whitespace by the parser."
ERROR: stale evidence at vacuum.c:171 - R-12218-18073
... in lang_vacuum.html: "A VACUUM will fail if there is an open transaction on the database connection that is attempting to run the VACUUM."
ERROR: stale evidence at vacuum.c:175 - R-15610-35227
... in lang_vacuum.html: "Unfinalized SQL statements typically hold a read transaction open, so the VACUUM might fail if there are unfinalized SQL statements on the same connection."
ERROR: stale evidence at vdbe.c:5573 - R-61914-48074
... in autoinc.html: "If the table is initially empty, then a ROWID of 1 is used."
ERROR: stale evidence at vdbe.c:5580 - R-29538-34987
... in autoinc.html: "The usual algorithm is to give the newly created row a ROWID that is one larger than the largest ROWID in the table prior to the insert."
ERROR: stale evidence at vdbe.c:5606 - R-17817-00630
... in autoinc.html: "If the largest possible ROWID has previously been inserted, then new INSERTs are not allowed and any attempt to insert a new row will fail with an SQLITE_FULL error."
ERROR: stale evidence at vdbe.c:5632 - R-38219-53002
... in autoinc.html: "If no unused ROWID can be found after a reasonable number of attempts, the insert operation fails with an SQLITE_FULL error."
ERROR: stale evidence at vdbe.c:5635 - R-40812-03570
... in autoinc.html: "If no negative ROWID values are inserted explicitly, then automatically generated ROWID values will always be greater than zero."
ERROR: stale evidence at vdbe.c:7773 - R-24505-23230
... in c3ref/context.html: "A pointer to an sqlite3_context object is always first parameter to application-defined SQL functions."
ERROR: stale evidence at vdbe.c:8716 - R-24505-23230
... in c3ref/context.html: "A pointer to an sqlite3_context object is always first parameter to application-defined SQL functions."
ERROR: stale evidence at vdbemem.c:510 - R-24505-23230
... in c3ref/context.html: "A pointer to an sqlite3_context object is always first parameter to application-defined SQL functions."
ERROR: stale evidence at vdbemem.c:1341 - R-31275-44060
... in c3ref/column_blob.html: "Strings returned by sqlite3_column_text() and sqlite3_column_text16(), even empty strings, are always zero-terminated."
ERROR: stale evidence at where.c:1615 - R-14553-25174
... in c3ref/vtab_rhs_value.html: "When xBestIndex returns, the sqlite3_value object returned by sqlite3_vtab_rhs_value() is automatically deallocated."
ERROR: stale evidence at where.c:4443 - R-30545-25046
... in c3ref/vtab_rhs_value.html: "The sqlite3_vtab_rhs_value() interface can return an result code other than SQLITE_OK or SQLITE_NOTFOUND if something goes wrong."
ERROR: stale evidence at where.c:4459 - R-19933-32160
... in c3ref/vtab_rhs_value.html: "The sqlite3_vtab_rhs_value(P,J,V) interface returns SQLITE_OK if and only if *V is set to a value."
ERROR: stale evidence at where.c:4460 - R-36424-56542
... in c3ref/vtab_rhs_value.html: "The sqlite3_vtab_rhs_value(P,J,V) inteface returns SQLITE_NOTFOUND if the right-hand side of the J-th constraint is not available."
ERROR: stale evidence at test_rtreedoc.c:142 - R-50437-53270
... in rtree.html: "The first argument is a pointer to an sqlite3_rtree_geometry structure which provides information about how the SQL function was invoked."
ERROR: stale evidence at test_rtreedoc.c:143 - R-02424-24769
... in rtree.html: "The second argument is the number of coordinates in each r-tree entry, and is always the same for any given R*Tree."
ERROR: stale evidence at test_rtreedoc.c:144 - R-00090-24248
... in rtree.html: "The third argument, aCoord[], is an array of nCoord coordinates that defines a bounding box to be tested."
ERROR: stale evidence at test_rtreedoc.c:145 - R-28207-40885
... in rtree.html: "The last argument is a pointer into which the callback result should be written."
ERROR: stale evidence at test_rtreedoc.c:157 - R-28207-40885
... in rtree.html: "The last argument is a pointer into which the callback result should be written."
ERROR: stale evidence at test_rtreedoc.c:163 - R-28207-40885
... in rtree.html: "The last argument is a pointer into which the callback result should be written."
ERROR: stale evidence at rtreedoc.test:475 - R-56987-45305
... in rtree.html: "So to insert some data into our sample R*Tree index, we can do something like this: INSERT INTO demo_index VALUES (28215, -80.781227, -80.604706, 35.208813, 35.297367), (28216, -80.957283, -80.840599, 35.235920, 35.367825), (28217, -80.960869, -80.869431, 35.133682, 35.208233), (28226, -80.878983, -80.778275, 35.060287, 35.154446), (28227, -80.745544, -80.555382, 35.130215, 35.236916), (28244, -80.844208, -80.841988, 35.223728, 35.225471), (28262, -80.809074, -80.682938, 35.276207, 35.377747), (28269, -80.851471, -80.735718, 35.272560, 35.407925), (28270, -80.794983, -80.728966, 35.059872, 35.161823), (28273, -80.994766, -80.875259, 35.074734, 35.172836), (28277, -80.876793, -80.767586, 35.001709, 35.101063), (28278, -81.058029, -80.956375, 35.044701, 35.223812), (28280, -80.844208, -80.841972, 35.225468, 35.227203), (28282, -80.846382, -80.844193, 35.223972, 35.225655);"
ERROR: stale evidence at rtreedoc.test:561 - R-49927-54202
... in rtree.html: "For example, the main office of the SQLite project is located at 35.37785, -80.77470. To find which zipcodes might service that office, one could right: SELECT id FROM demo_index WHERE minX<=-80.77470 AND maxX>=-80.77470 AND minY<=35.37785 AND maxY>=35.37785;"
ERROR: stale evidence at rtreedoc.test:1083 - R-05552-15084
... in rtree.html: "CREATE VIRTUAL TABLE demo_index2 USING rtree( id, -- Integer primary key minX, maxX, -- Minimum and maximum X coordinate minY, maxY, -- Minimum and maximum Y coordinate +objname TEXT, -- name of the object +objtype TEXT, -- object type +boundary BLOB -- detailed boundary of object );"
ERROR: stale evidence at rtreedoc2.test:61 - R-61427-46983
... in rtree.html: "For example, a query like the following might be used to find all R*Tree entries that overlap with a circle centered a 45.3,22.9 with a radius of 5.0: SELECT id FROM demo_index WHERE id MATCH circle(45.3, 22.9, 5.0)"
ERROR: stale evidence at cast.test:364 - R-24225-46995-38973-17701-37772-12518-00219-22558
ERROR: stale evidence at date3.test:51 - R-62992-54137-18704-21860-20022-25020-23814-10304
ERROR: stale evidence at date3.test:92 - R-38886-35357-61293-06392-16818-17229-57079-41544
ERROR: stale evidence at date3.test:97 - R-53132-26856-55284-61256-49129-35649-13500-14879
ERROR: stale evidence at date3.test:110 - R-49255-55373-50105-35704-52398-37600-44211-44389
ERROR: stale evidence at e_createtable.test:650 - R-64828-59568-61067-60898-36143-56429-01681-45331
ERROR: stale evidence at e_expr.test:268 - R-15904-00746-56156-46243-28663-24468-25045-59093
ERROR: stale evidence at e_fkey.test:190 - R-11255-19907
... in foreignkeys.html: "The following command-line session demonstrates this: sqlite> PRAGMA foreign_keys; 0 sqlite> PRAGMA foreign_keys = ON; sqlite> PRAGMA foreign_keys; 1 sqlite> PRAGMA foreign_keys = OFF; sqlite> PRAGMA foreign_keys; 0"
ERROR: stale evidence at e_fkey.test:433 - R-16127-35442
... in foreignkeys.html: "The following SQLite command-line session illustrates the effect of the foreign key constraint added to the track table: sqlite> SELECT * FROM artist; artistid artistname -------- ----------------- 1 Dean Martin 2 Frank Sinatra sqlite> SELECT * FROM track; trackid trackname trackartist ------- ----------------- ----------- 11 That's Amore 1 12 Christmas Blues 1 13 My Way 2 sqlite> -- This fails because the value inserted into the trackartist column (3) sqlite> -- does not correspond to row in the artist table. sqlite> INSERT INTO track VALUES(14, 'Mr. Bojangles', 3); SQL error: foreign key constraint failed sqlite> -- This succeeds because a NULL is inserted into trackartist. A sqlite> -- corresponding row in the artist table is not required in this case. sqlite> INSERT INTO track VALUES(14, 'Mr. Bojangles', NULL); sqlite> -- Trying to modify the trackartist field of the record after it has sqlite> -- been inserted does not work either, since the new value of trackartist (3) sqlite> -- Still does not correspond to any row in the artist table. sqlite> UPDATE track SET trackartist = 3 WHERE trackname = 'Mr. Bojangles'; SQL error: foreign key constraint failed sqlite> -- Insert the required row into the artist table. It is then possible to sqlite> -- update the inserted row to set trackartist to 3 (since a corresponding sqlite> -- row in the artist table now exists). sqlite> INSERT INTO artist VALUES(3, 'Sammy Davis Jr.'); sqlite> UPDATE track SET trackartist = 3 WHERE trackname = 'Mr. Bojangles'; sqlite> -- Now that "Sammy Davis Jr." (artistid = 3) has been added to the database, sqlite> -- it is possible to INSERT new tracks using this artist without violating sqlite> -- the foreign key constraint: sqlite> INSERT INTO track VALUES(15, 'Boogie Woogie', 3);"
ERROR: stale evidence at e_fkey.test:477 - R-15958-50233
... in foreignkeys.html: "As you would expect, it is not possible to manipulate the database to a state that violates the foreign key constraint by deleting or updating rows in the artist table either: sqlite> -- Attempting to delete the artist record for "Frank Sinatra" fails, since sqlite> -- the track table contains a row that refer to it. sqlite> DELETE FROM artist WHERE artistname = 'Frank Sinatra'; SQL error: foreign key constraint failed sqlite> -- Delete all the records from the track table that refer to the artist sqlite> -- "Frank Sinatra". Only then is it possible to delete the artist. sqlite> DELETE FROM track WHERE trackname = 'My Way'; sqlite> DELETE FROM artist WHERE artistname = 'Frank Sinatra'; sqlite> -- Try to update the artistid of a row in the artist table while there sqlite> -- exists records in the track table that refer to it. sqlite> UPDATE artist SET artistid=4 WHERE artistname = 'Dean Martin'; SQL error: foreign key constraint failed sqlite> -- Once all the records that refer to a row in the artist table have sqlite> -- been deleted, it is possible to modify the artistid of the row. sqlite> DELETE FROM track WHERE trackname IN('That''s Amore', 'Christmas Blues'); sqlite> UPDATE artist SET artistid=4 WHERE artistname = 'Dean Martin';"
ERROR: stale evidence at e_fkey.test:671 - R-27484-01467
... in foreignkeys.html: "For example, CREATE TABLE parent(a PRIMARY KEY, b UNIQUE, c, d, e, f); CREATE UNIQUE INDEX i1 ON parent(c, d); CREATE INDEX i2 ON parent(e); CREATE UNIQUE INDEX i3 ON parent(f COLLATE nocase); CREATE TABLE child1(f, g REFERENCES parent(a)); -- Ok CREATE TABLE child2(h, i REFERENCES parent(b)); -- Ok CREATE TABLE child3(j, k, FOREIGN KEY(j, k) REFERENCES parent(c, d)); -- Ok CREATE TABLE child4(l, m REFERENCES parent(e)); -- Error! CREATE TABLE child5(n, o REFERENCES parent(f)); -- Error! CREATE TABLE child6(p, q, FOREIGN KEY(p, q) REFERENCES parent(b, c)); -- Error! CREATE TABLE child7(r REFERENCES parent(c)); -- Error! The foreign key constraints created as part of tables child1, child2 and child3 are all fine."
ERROR: stale evidence at e_fkey.test:818 - R-19353-43643
... in foreignkeys.html: "The last bullet above is illustrated by the following: CREATE TABLE parent2(a, b, PRIMARY KEY(a,b)); CREATE TABLE child8(x, y, FOREIGN KEY(x,y) REFERENCES parent2); -- Ok CREATE TABLE child9(x REFERENCES parent2); -- Error! CREATE TABLE child10(x,y,z, FOREIGN KEY(x,y,z) REFERENCES parent2); -- Error!"
ERROR: stale evidence at e_fkey.test:965 - R-00279-52283
... in foreignkeys.html: "Returning to the example in section 1, each time an application deletes a row from the artist table (the parent table), it performs the equivalent of the following SELECT statement to search for referencing rows in the track table (the child table). SELECT rowid FROM track WHERE trackartist = ? where ? in the above is replaced with the value of the artistid column of the record being deleted from the artist table (recall that the trackartist column is the child key and the artistid column is the parent key)."
ERROR: stale evidence at e_fkey.test:1093 - R-14553-34013
... in foreignkeys.html: "the complete database schema for efficient implementation of the foreign key constraint might be: CREATE TABLE artist( artistid INTEGER PRIMARY KEY, artistname TEXT ); CREATE TABLE track( trackid INTEGER, trackname TEXT, trackartist INTEGER REFERENCES artist ); CREATE INDEX trackindex ON track(trackartist);"
ERROR: stale evidence at e_fkey.test:1184 - R-24676-09859
... in foreignkeys.html: "For example, consider the following database schema: CREATE TABLE album( albumartist TEXT, albumname TEXT, albumcover BINARY, PRIMARY KEY(albumartist, albumname) ); CREATE TABLE song( songid INTEGER, songartist TEXT, songalbum TEXT, songname TEXT, FOREIGN KEY(songartist, songalbum) REFERENCES album(albumartist, albumname) ); In this system, each entry in the song table is required to map to an entry in the album table with the same combination of artist and album."
ERROR: stale evidence at e_fkey.test:1364 - R-12782-61841
... in foreignkeys.html: "To mark a foreign key constraint as deferred, its declaration must include the following clause: DEFERRABLE INITIALLY DEFERRED -- A deferred foreign key constraint"
ERROR: stale evidence at e_fkey.test:1371 - R-09005-28791
... in foreignkeys.html: "Replacing the phrase above with any of the following creates an immediate foreign key constraint. NOT DEFERRABLE INITIALLY DEFERRED -- An immediate foreign key constraint NOT DEFERRABLE INITIALLY IMMEDIATE -- An immediate foreign key constraint NOT DEFERRABLE -- An immediate foreign key constraint DEFERRABLE INITIALLY IMMEDIATE -- An immediate foreign key constraint DEFERRABLE -- An immediate foreign key constraint"
ERROR: stale evidence at e_fkey.test:1486 - R-24499-57071
... in foreignkeys.html: "The following example illustrates the effect of using a deferred foreign key constraint. -- Database schema. Both tables are initially empty. CREATE TABLE artist( artistid INTEGER PRIMARY KEY, artistname TEXT ); CREATE TABLE track( trackid INTEGER, trackname TEXT, trackartist INTEGER REFERENCES artist(artistid) DEFERRABLE INITIALLY DEFERRED ); sqlite3> -- If the foreign key constraint were immediate, this INSERT would sqlite3> -- cause an error (since as there is no row in table artist with sqlite3> -- artistid=5). But as the constraint is deferred and there is an sqlite3> -- open transaction, no error occurs. sqlite3> BEGIN; sqlite3> INSERT INTO track VALUES(1, 'White Christmas', 5); sqlite3> -- The following COMMIT fails, as the database is in a state that sqlite3> -- does not satisfy the deferred foreign key constraint. The sqlite3> -- transaction remains open. sqlite3> COMMIT; SQL error: foreign key constraint failed sqlite3> -- After inserting a row into the artist table with artistid=5, the sqlite3> -- deferred foreign key constraint is satisfied. It is then possible sqlite3> -- to commit the transaction without error. sqlite3> INSERT INTO artist VALUES(5, 'Bing Crosby'); sqlite3> COMMIT;"
ERROR: stale evidence at e_fkey.test:2185 - R-65058-57158
... in foreignkeys.html: "For example, adding an "ON UPDATE CASCADE" clause to the foreign key as shown below enhances the example schema from section 1 to allow the user to update the artistid (the parent key of the foreign key constraint) column without breaking referential integrity: -- Database schema CREATE TABLE artist( artistid INTEGER PRIMARY KEY, artistname TEXT ); CREATE TABLE track( trackid INTEGER, trackname TEXT, trackartist INTEGER REFERENCES artist(artistid) ON UPDATE CASCADE ); sqlite> SELECT * FROM artist; artistid artistname -------- ----------------- 1 Dean Martin 2 Frank Sinatra sqlite> SELECT * FROM track; trackid trackname trackartist ------- ----------------- ----------- 11 That's Amore 1 12 Christmas Blues 1 13 My Way 2 sqlite> -- Update the artistid column of the artist record for "Dean Martin". sqlite> -- Normally, this would raise a constraint, as it would orphan the two sqlite> -- dependent records in the track table. However, the ON UPDATE CASCADE clause sqlite> -- attached to the foreign key definition causes the update to "cascade" sqlite> -- to the child table, preventing the foreign key constraint violation. sqlite> UPDATE artist SET artistid = 100 WHERE artistname = 'Dean Martin'; sqlite> SELECT * FROM artist; artistid artistname -------- ----------------- 2 Frank Sinatra 100 Dean Martin sqlite> SELECT * FROM track; trackid trackname trackartist ------- ----------------- ----------- 11 That's Amore 100 12 Christmas Blues 100 13 My Way 2"
ERROR: stale evidence at e_fkey.test:2264 - R-11856-19836
... in foreignkeys.html: "For example: -- Database schema CREATE TABLE artist( artistid INTEGER PRIMARY KEY, artistname TEXT ); CREATE TABLE track( trackid INTEGER, trackname TEXT, trackartist INTEGER DEFAULT 0 REFERENCES artist(artistid) ON DELETE SET DEFAULT ); sqlite> SELECT * FROM artist; artistid artistname -------- ----------------- 3 Sammy Davis Jr. sqlite> SELECT * FROM track; trackid trackname trackartist ------- ----------------- ----------- 14 Mr. Bojangles 3 sqlite> -- Deleting the row from the parent table causes the child key sqlite> -- value of the dependent row to be set to integer value 0. However, this sqlite> -- value does not correspond to any row in the parent table. Therefore sqlite> -- the foreign key constraint is violated and an is exception thrown. sqlite> DELETE FROM artist WHERE artistname = 'Sammy Davis Jr.'; SQL error: foreign key constraint failed sqlite> -- This time, the value 0 does correspond to a parent table row. And sqlite> -- so the DELETE statement does not violate the foreign key constraint sqlite> -- and no exception is thrown. sqlite> INSERT INTO artist VALUES(0, 'Unknown Artist'); sqlite> DELETE FROM artist WHERE artistname = 'Sammy Davis Jr.'; sqlite> SELECT * FROM artist; artistid artistname -------- ----------------- 0 Unknown Artist sqlite> SELECT * FROM track; trackid trackname trackartist ------- ----------------- ----------- 14 Mr. Bojangles 0"
ERROR: stale evidence at e_fkey.test:2310 - R-09564-22170
... in foreignkeys.html: "Whenever a row in the parent table of a foreign key constraint is deleted, or when the values stored in the parent key column or columns are modified, the logical sequence of events is: Execute applicable BEFORE trigger programs, Check local (non foreign key) constraints, Update or delete the row in the parent table, Perform any required foreign key actions, Execute applicable AFTER trigger programs."
ERROR: stale evidence at e_fkey.test:2418 - R-35129-58141
... in foreignkeys.html: "For example: -- Database schema CREATE TABLE parent(x PRIMARY KEY); CREATE TABLE child(y REFERENCES parent ON UPDATE SET NULL); sqlite> SELECT * FROM parent; x ---- key sqlite> SELECT * FROM child; y ---- key sqlite> -- Since the following UPDATE statement does not actually modify sqlite> -- the parent key value, the ON UPDATE action is not performed and sqlite> -- the child key value is not set to NULL. sqlite> UPDATE parent SET x = 'key'; sqlite> SELECT IFNULL(y, 'null') FROM child; y ---- key sqlite> -- This time, since the UPDATE statement does modify the parent key sqlite> -- value, the ON UPDATE action is performed and the child key is set sqlite> -- to NULL. sqlite> UPDATE parent SET x = 'key2'; sqlite> SELECT IFNULL(y, 'null') FROM child; y ---- null"
ERROR: stale evidence at e_resolve.test:111 - R-37286-42536
... in lang_naming.html: "/* Add a table named 't1' to the temp, main and an attached database */ ATTACH 'file.db' AS aux; CREATE TABLE t1(x, y); CREATE TEMP TABLE t1(x, y); CREATE TABLE aux.t1(x, y); DROP TABLE t1; /* Drop table in temp database */ DROP TABLE t1; /* Drop table in main database */ DROP TABLE t1; /* Drop table in aux database */"
Generating requirements matrix...
Translating documentation.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
./tclsh.docsrc ./remove_carets.tcl ./doc/'*.html' ./doc/c3ref/'*.html' ./doc/session/'*.html'
Removing ^( )^ and ^ from 225 of 486 files.
./tclsh.docsrc ./search/mkscript.tcl ./search/search.tcl.in >doc/search
chmod 744 doc/search
mkdir -p ./doc/search.d/
./tclsh.docsrc ./search/mkscript.tcl ./search/admin.tcl.in >doc/search.d/admin
chmod 744 ./doc/search.d/admin
./tclsh.docsrc ./search/buildsearchdb.tcl
Indexing releaselog/3_48_0.html...
Indexing releaselog/3_47_0.html...
Indexing releaselog/3_46_1.html...
Indexing releaselog/3_46_0.html...
Indexing releaselog/3_45_3.html...
Indexing releaselog/3_45_2.html...
Indexing releaselog/3_45_1.html...
Indexing releaselog/3_45_0.html...
Indexing releaselog/3_44_2.html...
Indexing releaselog/3_44_1.html...
Indexing releaselog/3_44_0.html...
Indexing releaselog/3_43_2.html...
Indexing releaselog/3_43_1.html...
Indexing releaselog/3_43_0.html...
Indexing releaselog/3_42_0.html...
Indexing releaselog/3_41_2.html...
Indexing releaselog/3_41_1.html...
Indexing releaselog/3_41_0.html...
Indexing releaselog/3_40_1.html...
Indexing releaselog/3_40_0.html...
Indexing releaselog/3_39_4.html...
Indexing releaselog/3_39_3.html...
Indexing releaselog/3_39_2.html...
Indexing releaselog/3_39_1.html...
Indexing releaselog/3_39_0.html...
Indexing releaselog/3_38_5.html...
Indexing releaselog/3_38_4.html...
Indexing releaselog/3_38_3.html...
Indexing releaselog/3_38_2.html...
Indexing releaselog/3_38_1.html...
Indexing releaselog/3_38_0.html...
Indexing releaselog/3_37_2.html...
Indexing releaselog/3_37_1.html...
Indexing releaselog/3_37_0.html...
Indexing releaselog/3_36_0.html...
Indexing releaselog/3_35_5.html...
Indexing releaselog/3_35_4.html...
Indexing releaselog/3_35_3.html...
Indexing releaselog/3_35_2.html...
Indexing releaselog/3_35_1.html...
Indexing releaselog/3_35_0.html...
Indexing releaselog/3_34_1.html...
Indexing releaselog/3_34_0.html...
Indexing releaselog/3_33_0.html...
Indexing releaselog/3_32_3.html...
Indexing releaselog/3_32_2.html...
Indexing releaselog/3_32_1.html...
Indexing releaselog/3_32_0.html...
Indexing releaselog/3_31_1.html...
Indexing releaselog/3_31_0.html...
Indexing releaselog/3_30_1.html...
Indexing releaselog/3_30_0.html...
Indexing releaselog/3_29_0.html...
Indexing releaselog/3_28_0.html...
Indexing releaselog/3_27_2.html...
Indexing releaselog/3_27_1.html...
Indexing releaselog/3_27_0.html...
Indexing releaselog/3_26_0.html...
Indexing releaselog/3_25_3.html...
Indexing releaselog/3_25_2.html...
Indexing releaselog/3_25_1.html...
Indexing releaselog/3_25_0.html...
Indexing releaselog/3_24_0.html...
Indexing releaselog/3_23_1.html...
Indexing releaselog/3_23_0.html...
Indexing releaselog/3_22_0.html...
Indexing releaselog/3_21_0.html...
Indexing releaselog/3_20_1.html...
Indexing releaselog/3_20_0.html...
Indexing releaselog/3_19_3.html...
Indexing releaselog/3_19_2.html...
Indexing releaselog/3_19_1.html...
Indexing releaselog/3_19_0.html...
Indexing releaselog/3_18_2.html...
Indexing releaselog/3_18_1.html...
Indexing releaselog/3_18_0.html...
Indexing releaselog/3_17_0.html...
Indexing releaselog/3_16_2.html...
Indexing releaselog/3_16_1.html...
Indexing releaselog/3_16_0.html...
Indexing releaselog/3_15_2.html...
Indexing releaselog/3_15_1.html...
Indexing releaselog/3_15_0.html...
Indexing releaselog/3_14_2.html...
Indexing releaselog/3_14_1.html...
Indexing releaselog/3_14.html...
Indexing releaselog/3_13_0.html...
Indexing releaselog/3_12_2.html...
Indexing releaselog/3_12_1.html...
Indexing releaselog/3_12_0.html...
Indexing releaselog/3_11_1.html...
Indexing releaselog/3_11_0.html...
Indexing releaselog/3_10_2.html...
Indexing releaselog/3_10_1.html...
Indexing releaselog/3_10_0.html...
Indexing releaselog/3_9_3.html...
Indexing releaselog/3_9_2.html...
Indexing releaselog/3_9_1.html...
Indexing releaselog/3_9_0.html...
Indexing releaselog/3_8_11_1.html...
Indexing releaselog/3_8_11.html...
Indexing releaselog/3_8_10_2.html...
Indexing releaselog/3_8_10_1.html...
Indexing releaselog/3_8_10.html...
Indexing releaselog/3_8_9.html...
Indexing releaselog/3_8_8_3.html...
Indexing releaselog/3_8_8_2.html...
Indexing releaselog/3_8_8_1.html...
Indexing releaselog/3_8_8.html...
Indexing releaselog/3_8_7_4.html...
Indexing releaselog/3_8_7_3.html...
Indexing releaselog/3_8_7_2.html...
Indexing releaselog/3_8_7_1.html...
Indexing releaselog/3_8_7.html...
Indexing releaselog/3_8_6.html...
Indexing releaselog/3_8_5.html...
Indexing releaselog/3_8_4_3.html...
Indexing releaselog/3_8_4_2.html...
Indexing releaselog/3_8_4_1.html...
Indexing releaselog/3_8_4.html...
Indexing releaselog/3_8_3_1.html...
Indexing releaselog/3_8_3.html...
Indexing releaselog/3_8_2.html...
Indexing releaselog/3_8_1.html...
Indexing releaselog/3_8_0_2.html...
Indexing releaselog/3_8_0_1.html...
Indexing releaselog/3_8_0.html...
Indexing releaselog/3_7_17.html...
Indexing releaselog/3_7_16_2.html...
Indexing releaselog/3_7_16_1.html...
Indexing releaselog/3_7_16.html...
Indexing releaselog/3_7_15_2.html...
Indexing releaselog/3_7_15_1.html...
Indexing releaselog/3_7_15.html...
Indexing releaselog/3_7_14_1.html...
Indexing releaselog/3_7_14.html...
Indexing releaselog/3_7_13.html...
Indexing releaselog/3_7_12_1.html...
Indexing releaselog/3_7_12.html...
Indexing releaselog/3_7_11.html...
Indexing releaselog/3_7_10.html...
Indexing releaselog/3_7_9.html...
Indexing releaselog/3_7_8.html...
Indexing releaselog/3_7_7_1.html...
Indexing releaselog/3_7_7.html...
Indexing releaselog/3_7_6_3.html...
Indexing releaselog/3_7_6_2.html...
Indexing releaselog/3_7_6_1.html...
Indexing releaselog/3_7_6.html...
Indexing releaselog/3_7_5.html...
Indexing releaselog/3_7_4.html...
Indexing releaselog/3_7_3.html...
Indexing releaselog/3_7_2.html...
Indexing releaselog/3_7_1.html...
Indexing releaselog/3_7_0_1.html...
Indexing releaselog/3_7_0.html...
Indexing releaselog/3_6_23_1.html...
Indexing releaselog/3_6_23.html...
Indexing releaselog/3_6_22.html...
Indexing releaselog/3_6_21.html...
Indexing releaselog/3_6_20.html...
Indexing releaselog/3_6_19.html...
Indexing releaselog/3_6_18.html...
Indexing releaselog/3_6_17.html...
Indexing releaselog/3_6_16_1.html...
Indexing releaselog/3_6_16.html...
Indexing releaselog/3_6_15.html...
Indexing releaselog/3_6_14_2.html...
Indexing releaselog/3_6_14_1.html...
Indexing releaselog/3_6_14.html...
Indexing releaselog/3_6_13.html...
Indexing releaselog/3_6_12.html...
Indexing releaselog/3_6_11.html...
Indexing releaselog/3_6_10.html...
Indexing releaselog/3_6_9.html...
Indexing releaselog/3_6_8.html...
Indexing releaselog/3_6_7.html...
Indexing releaselog/3_6_6_2.html...
Indexing releaselog/3_6_6_1.html...
Indexing releaselog/3_6_6.html...
Indexing releaselog/3_6_5.html...
Indexing releaselog/3_6_4.html...
Indexing releaselog/3_6_3.html...
Indexing releaselog/3_6_2.html...
Indexing releaselog/3_6_1.html...
Indexing releaselog/3_6_0.html...
Indexing releaselog/3_5_9.html...
Indexing releaselog/3_5_8.html...
Indexing releaselog/3_5_7.html...
Indexing releaselog/3_5_6.html...
Indexing releaselog/3_5_5.html...
Indexing releaselog/3_5_4.html...
Indexing releaselog/3_5_3.html...
Indexing releaselog/3_5_2.html...
Indexing releaselog/3_5_1.html...
Indexing releaselog/3_5_0.html...
Indexing releaselog/3_4_2.html...
Indexing releaselog/3_4_1.html...
Indexing releaselog/3_4_0.html...
Indexing releaselog/3_3_17.html...
Indexing releaselog/3_3_16.html...
Indexing releaselog/3_3_15.html...
Indexing releaselog/3_3_14.html...
Indexing releaselog/3_3_13.html...
Indexing releaselog/3_3_12.html...
Indexing releaselog/3_3_11.html...
Indexing releaselog/3_3_10.html...
Indexing releaselog/3_3_9.html...
Indexing releaselog/3_3_8.html...
Indexing releaselog/3_3_7.html...
Indexing releaselog/3_3_6.html...
Indexing releaselog/3_3_5.html...
Indexing releaselog/3_3_4.html...
Indexing releaselog/3_3_3.html...
Indexing releaselog/3_3_2.html...
Indexing releaselog/3_3_1.html...
Indexing releaselog/3_3_0.html...
Indexing releaselog/3_2_8.html...
Indexing releaselog/3_2_7.html...
Indexing releaselog/3_2_6.html...
Indexing releaselog/3_2_5.html...
Indexing releaselog/3_2_4.html...
Indexing releaselog/3_2_3.html...
Indexing releaselog/3_2_2.html...
Indexing releaselog/3_2_1.html...
Indexing releaselog/3_2_0.html...
Indexing releaselog/3_1_6.html...
Indexing releaselog/3_1_5.html...
Indexing releaselog/3_1_4.html...
Indexing releaselog/3_1_3.html...
Indexing releaselog/3_1_2.html...
Indexing releaselog/3_1_1.html...
Indexing releaselog/3_1_0.html...
Indexing releaselog/3_0_8.html...
Indexing releaselog/3_0_7.html...
Indexing releaselog/3_0_6.html...
Indexing releaselog/3_0_5.html...
Indexing releaselog/3_0_4.html...
Indexing releaselog/3_0_3.html...
Indexing releaselog/3_0_2.html...
Indexing releaselog/3_0_1.html...
Indexing releaselog/3_0_0.html...
Indexing lang_with.html...
Indexing lang_vacuum.html...
Indexing lang_upsert.html...
Indexing lang_update.html...
Indexing lang_transaction.html...
Indexing lang_select.html...
Indexing lang_savepoint.html...
Indexing lang_returning.html...
Indexing lang_replace.html...
Indexing lang_reindex.html...
Indexing lang_naming.html...
Indexing lang_mathfunc.html...
Indexing lang_keywords.html...
Indexing lang_insert.html...
Indexing lang_indexedby.html...
Indexing lang_expr.html...
Indexing lang_explain.html...
Indexing lang_dropview.html...
Indexing lang_droptrigger.html...
Indexing lang_droptable.html...
Indexing lang_dropindex.html...
Indexing lang_detach.html...
Indexing lang_delete.html...
Indexing lang_datefunc.html...
Indexing lang_createvtab.html...
Indexing lang_createview.html...
Indexing lang_createtrigger.html...
Indexing lang_createtable.html...
Indexing lang_createindex.html...
Indexing lang_corefunc.html...
Indexing lang_conflict.html...
Indexing lang_comment.html...
Indexing lang_attach.html...
Indexing lang_analyze.html...
Indexing lang_altertable.html...
Indexing lang_aggfunc.html...
Indexing c3ref/free.html...
Indexing c3ref/exec.html...
Indexing c3ref/mprintf.html...
Indexing c3ref/io_methods.html...
Indexing c3ref/create_function.html...
Indexing c3ref/file_control.html...
Indexing c3ref/column_blob.html...
Indexing c3ref/busy_handler.html...
Indexing c3ref/get_autocommit.html...
Indexing c3ref/set_authorizer.html...
Indexing c3ref/prepare.html...
Indexing c3ref/bind_blob.html...
Indexing c3ref/win32_set_directory.html...
Indexing c3ref/vtab_in_first.html...
Indexing c3ref/vfs_find.html...
Indexing c3ref/value_dup.html...
Indexing c3ref/value_blob.html...
Indexing c3ref/uri_boolean.html...
Indexing c3ref/total_changes.html...
Indexing c3ref/stricmp.html...
Indexing c3ref/str_errcode.html...
Indexing c3ref/str_append.html...
Indexing c3ref/stmt_scanstatus.html...
Indexing c3ref/status.html...
Indexing c3ref/result_blob.html...
Indexing c3ref/profile.html...
Indexing c3ref/preupdate_blobwrite.html...
Indexing c3ref/open.html...
Indexing c3ref/mutex_held.html...
Indexing c3ref/mutex_alloc.html...
Indexing c3ref/memory_highwater.html...
Indexing c3ref/libversion.html...
Indexing c3ref/keyword_check.html...
Indexing c3ref/interrupt.html...
Indexing c3ref/initialize.html...
Indexing c3ref/hard_heap_limit64.html...
Indexing c3ref/get_clientdata.html...
Indexing c3ref/get_auxdata.html...
Indexing c3ref/free_table.html...
Indexing c3ref/filename_database.html...
Indexing c3ref/expanded_sql.html...
Indexing c3ref/errcode.html...
Indexing c3ref/create_module.html...
Indexing c3ref/create_filename.html...
Indexing c3ref/create_collation.html...
Indexing c3ref/complete.html...
Indexing c3ref/compileoption_get.html...
Indexing c3ref/commit_hook.html...
Indexing c3ref/column_name.html...
Indexing c3ref/column_decltype.html...
Indexing c3ref/column_database_name.html...
Indexing c3ref/collation_needed.html...
Indexing c3ref/close.html...
Indexing c3ref/changes.html...
Indexing c3ref/backup_finish.html...
Indexing c3ref/aggregate_count.html...
Indexing c3ref/value.html...
Indexing c3ref/stmt.html...
Indexing c3ref/pcache_methods2.html...
Indexing c3ref/str.html...
Indexing c3ref/sqlite3.html...
Indexing c3ref/blob.html...
Indexing c3ref/vtab_cursor.html...
Indexing c3ref/module.html...
Indexing c3ref/int64.html...
Indexing c3ref/snapshot.html...
Indexing c3ref/c_stmtstatus_counter.html...
Indexing c3ref/c_dbstatus_options.html...
Indexing c3ref/c_limit_attached.html...
Indexing c3ref/c_win32_data_directory_type.html...
Indexing c3ref/c_vtab_constraint_support.html...
Indexing c3ref/c_txn_none.html...
Indexing c3ref/c_trace.html...
Indexing c3ref/c_testctrl_always.html...
Indexing c3ref/c_sync_dataonly.html...
Indexing c3ref/c_status_malloc_count.html...
Indexing c3ref/c_static.html...
Indexing c3ref/c_source_id.html...
Indexing c3ref/c_shm_exclusive.html...
Indexing c3ref/c_scanstat_est.html...
Indexing c3ref/c_scanstat_complex.html...
Indexing c3ref/c_prepare_normalize.html...
Indexing c3ref/c_open_autoproxy.html...
Indexing c3ref/c_mutex_fast.html...
Indexing c3ref/c_lock_exclusive.html...
Indexing c3ref/c_iocap_atomic.html...
Indexing c3ref/c_index_scan_hex.html...
Indexing c3ref/c_index_constraint_eq.html...
Indexing c3ref/c_fcntl_begin_atomic_write.html...
Indexing c3ref/c_fail.html...
Indexing c3ref/c_deterministic.html...
Indexing c3ref/c_deserialize_freeonclose.html...
Indexing c3ref/c_deny.html...
Indexing c3ref/c_dbconfig_defensive.html...
Indexing c3ref/c_config_covering_index_scan.html...
Indexing c3ref/c_checkpoint_full.html...
Indexing c3ref/c_blob.html...
Indexing c3ref/c_any.html...
Indexing c3ref/c_alter_table.html...
Indexing c3ref/c_access_exists.html...
Indexing c3ref/c_abort_rollback.html...
Indexing c3ref/c_abort.html...
Indexing c3ref/wal_hook.html...
Indexing c3ref/wal_checkpoint_v2.html...
Indexing c3ref/wal_checkpoint.html...
Indexing c3ref/wal_autocheckpoint.html...
Indexing c3ref/vtab_rhs_value.html...
Indexing c3ref/vtab_on_conflict.html...
Indexing c3ref/vtab_nochange.html...
Indexing c3ref/vtab_in.html...
Indexing c3ref/vtab_distinct.html...
Indexing c3ref/vtab_config.html...
Indexing c3ref/vtab_collation.html...
Indexing c3ref/value_subtype.html...
Indexing c3ref/value_encoding.html...
Indexing c3ref/user_data.html...
Indexing c3ref/update_hook.html...
Indexing c3ref/unlock_notify.html...
Indexing c3ref/txn_state.html...
Indexing c3ref/trace_v2.html...
Indexing c3ref/threadsafe.html...
Indexing c3ref/test_control.html...
Indexing c3ref/table_column_metadata.html...
Indexing c3ref/system_errno.html...
Indexing c3ref/strlike.html...
Indexing c3ref/strglob.html...
Indexing c3ref/str_new.html...
Indexing c3ref/str_finish.html...
Indexing c3ref/stmt_status.html...
Indexing c3ref/stmt_scanstatus_reset.html...
Indexing c3ref/stmt_readonly.html...
Indexing c3ref/stmt_isexplain.html...
Indexing c3ref/stmt_explain.html...
Indexing c3ref/stmt_busy.html...
Indexing c3ref/step.html...
Indexing c3ref/soft_heap_limit.html...
Indexing c3ref/snapshot_recover.html...
Indexing c3ref/snapshot_open.html...
Indexing c3ref/snapshot_get.html...
Indexing c3ref/snapshot_free.html...
Indexing c3ref/snapshot_cmp.html...
Indexing c3ref/sleep.html...
Indexing c3ref/set_last_insert_rowid.html...
Indexing c3ref/serialize.html...
Indexing c3ref/result_subtype.html...
Indexing c3ref/reset_auto_extension.html...
Indexing c3ref/reset.html...
Indexing c3ref/release_memory.html...
Indexing c3ref/randomness.html...
Indexing c3ref/progress_handler.html...
Indexing c3ref/overload_function.html...
Indexing c3ref/next_stmt.html...
Indexing c3ref/log.html...
Indexing c3ref/load_extension.html...
Indexing c3ref/limit.html...
Indexing c3ref/last_insert_rowid.html...
Indexing c3ref/finalize.html...
Indexing c3ref/extended_result_codes.html...
Indexing c3ref/enable_shared_cache.html...
Indexing c3ref/enable_load_extension.html...
Indexing c3ref/drop_modules.html...
Indexing c3ref/deserialize.html...
Indexing c3ref/declare_vtab.html...
Indexing c3ref/db_status.html...
Indexing c3ref/db_release_memory.html...
Indexing c3ref/db_readonly.html...
Indexing c3ref/db_name.html...
Indexing c3ref/db_mutex.html...
Indexing c3ref/db_handle.html...
Indexing c3ref/db_filename.html...
Indexing c3ref/db_config.html...
Indexing c3ref/db_cacheflush.html...
Indexing c3ref/database_file_object.html...
Indexing c3ref/data_count.html...
Indexing c3ref/context_db_handle.html...
Indexing c3ref/config.html...
Indexing c3ref/column_count.html...
Indexing c3ref/clear_bindings.html...
Indexing c3ref/cancel_auto_extension.html...
Indexing c3ref/busy_timeout.html...
Indexing c3ref/blob_write.html...
Indexing c3ref/blob_reopen.html...
Indexing c3ref/blob_read.html...
Indexing c3ref/blob_open.html...
Indexing c3ref/blob_close.html...
Indexing c3ref/blob_bytes.html...
Indexing c3ref/bind_parameter_name.html...
Indexing c3ref/bind_parameter_index.html...
Indexing c3ref/bind_parameter_count.html...
Indexing c3ref/autovacuum_pages.html...
Indexing c3ref/auto_extension.html...
Indexing c3ref/aggregate_context.html...
Indexing c3ref/vtab.html...
Indexing c3ref/vfs.html...
Indexing c3ref/temp_directory.html...
Indexing c3ref/pcache_page.html...
Indexing c3ref/pcache.html...
Indexing c3ref/mutex_methods.html...
Indexing c3ref/mutex.html...
Indexing c3ref/mem_methods.html...
Indexing c3ref/index_info.html...
Indexing c3ref/filename.html...
Indexing c3ref/file.html...
Indexing c3ref/data_directory.html...
Indexing c3ref/context.html...
Indexing c3ref/backup.html...
Indexing c3ref/api_routines.html...
Indexing c3ref/c_shm_nlock.html...
Indexing c3ref/c_serialize_nocopy.html...
Indexing c3ref/experimental.html...
Indexing c3ref/intro.html...
Indexing fileformat.html...
Indexing zipfile.html...
Indexing zeroconf.html...
Indexing withoutrowid.html...
Indexing windowfunctions.html...
Indexing whynotgit.html...
Indexing whyc.html...
Indexing whybytecode.html...
Indexing whentouse.html...
Indexing walformat.html...
Indexing wal.html...
Indexing vtablist.html...
Indexing vtab.html...
Indexing vfs.html...
Indexing versionnumbers.html...
Indexing version3.html...
Indexing vdbe.html...
Indexing useovernet.html...
Indexing uri.html...
Indexing unlock_notify.html...
Indexing unionvtab.html...
Indexing undoredo.html...
Indexing uintcseq.html...
Indexing transactional.html...
Indexing threadsafe.html...
Indexing th3.html...
Indexing testing.html...
Indexing tempfiles.html...
Indexing tclsqlite.html...
Indexing syntaxdiagrams.html...
Indexing syntax.html...
Indexing swarmvtab.html...
Indexing support.html...
Indexing stricttables.html...
Indexing stmt.html...
Indexing sqldiff.html...
Indexing sqlar.html...
Indexing sqlanalyze.html...
Indexing spellfix1.html...
Indexing speed.html...
Indexing shortnames.html...
Indexing sharedcache.html...
Indexing sessionintro.html...
Indexing session.html...
Indexing serverless.html...
Indexing series.html...
Indexing selfcontained.html...
Indexing security.html...
Indexing schematab.html...
Indexing rtree.html...
Indexing rsync.html...
Indexing rowvalue.html...
Indexing rowidtable.html...
Indexing rescode.html...
Indexing recovery.html...
Indexing rbu.html...
Indexing quirks.html...
Indexing quickstart.html...
Indexing queryplanner.html...
Indexing queryplanner-ng.html...
Indexing qmplan.html...
Indexing psow.html...
Indexing prosupport.html...
Indexing profile.html...
Indexing privatebranch.html...
Indexing printf.html...
Indexing pragma.html...
Indexing pgszchng2016.html...
Indexing percentile.html...
Indexing partialindex.html...
Indexing optoverview.html...
Indexing opcode.html...
Indexing onefile.html...
Indexing omitted.html...
Indexing oldnews.html...
Indexing nulls.html...
Indexing nulinstr.html...
Indexing np1queryprob.html...
Indexing news.html...
Indexing mostdeployed.html...
Indexing mmap.html...
Indexing memstat.html...
Indexing malloc.html...
Indexing lts.html...
Indexing locrsf.html...
Indexing lockingv3.html...
Indexing loadext.html...
Indexing limits.html...
Indexing lemon.html...
Indexing lang.html...
Indexing json1.html...
Indexing isolation.html...
Indexing invalidutf.html...
Indexing intern-v-extern-blob.html...
Indexing inmemorydb.html...
Indexing imposter.html...
Indexing hp1.html...
Indexing howtocorrupt.html...
Indexing howtocompile.html...
Indexing howitworks.html...
Indexing hirely.html...
Indexing getthecode.html...
Indexing geopoly.html...
Indexing gencol.html...
Indexing fullsql.html...
Indexing fts5.html...
Indexing fts3.html...
Indexing formatchng.html...
Indexing foreignkeys.html...
Indexing footprint.html...
Indexing floatingpoint.html...
Indexing flextypegood.html...
Indexing features.html...
Indexing fasterthanfs.html...
Indexing faq.html...
Indexing famous.html...
Indexing expridx.html...
Indexing errlog.html...
Indexing eqp.html...
Indexing download.html...
Indexing different.html...
Indexing deterministic.html...
Indexing debugging.html...
Indexing dbstat.html...
Indexing dbpage.html...
Indexing dbhash.html...
Indexing datatypes.html...
Indexing datatype3.html...
Indexing cves.html...
Indexing custombuild.html...
Indexing csv.html...
Indexing crew.html...
Indexing cpu.html...
Indexing copyright.html...
Indexing consortium.html...
Indexing conflict.html...
Indexing completion.html...
Indexing compile.html...
Indexing cli.html...
Indexing cksumvfs.html...
Indexing cintro.html...
Indexing chronology.html...
Indexing carray.html...
Indexing capi3.html...
Indexing c_interface.html...
Indexing bytecodevtab.html...
Indexing books.html...
Indexing bindptr.html...
Indexing base85.html...
Indexing base64.html...
Indexing backup.html...
Indexing autoinc.html...
Indexing atomiccommit.html...
Indexing asyncvfs.html...
Indexing assert.html...
Indexing arch.html...
Indexing appfunc.html...
Indexing appfileformat.html...
Indexing amalgamation.html...
Indexing affcase1.html...
Indexing aff_short.html...
Indexing about.html...
Indexing 35to36.html...
Indexing 34to35.html...
Indexing sqlite.html...
Indexing pressrelease-20071212.html...
Indexing copyright-release.html...
Indexing consortium_agreement-20071201.html...
==================================

(2) By userABCD on 2024-11-02 20:23:18 in reply to 1 [link] [source] 

Is my build script making the errors appear? Is there a way to fix it?

(3) By Larry Brasfield (larrybr) on 2024-11-02 23:58:45 in reply to 2 [source]

To get just the docs, cleanly, enter "make fast".

The evidence markers, which link claims in the docs to tests in the test suite, are often slightly behind for a while after feature development. Build errors involving them generally mean only that the doc language was enhanced without updating the marker values. They need not be your worry.

(4) By userABCD on 2024-11-27 15:18:42 in reply to 1 [link] [source] 

I still get multiple "ERROR: stale evidence at ..." outputs.

I am building using the latest version at time of writing. Which pair of checkouts can I use to get a clean build? Is it safe to always use the latest versions? 

This are the current pair of checkouts I tried:

project-name: SQLite
repository:   /home/userABCD/sqlite.fossil
local-root:   /dev/shm/sqlite/
config-db:    /home/userABCD/.fossil
project-code: 2ab58778c2967968b94284e989e43dc11791f548
checkout:     1e405c39a8405e2081ce061559d1aacc70055fc7 2024-11-26 23:40:54 UTC
parent:       41b79bde4a4b6510b41cc9175ff2527fbd3ca920 2024-11-26 20:46:18 UTC
merged-from:  f1cb1a815a09d71eb52d5c7f2f4e5c7689535232 2024-11-26 23:30:49 UTC
tags:         trunk
comment:      Allow the iif() function to work with two arguments. The third argument is then
              assumed to be NULL. Also allow if() as an alternative spelling for iif(). (user: drh)
check-ins:    32860

project-name: Documentation Source Text
repository:   /home/userABCD/sqliteDoc.fossil
local-root:   /dev/shm/sqliteDoc/
config-db:    /home/userABCD/.fossil
project-code: a49a74a282acfe2f07de91768b854dffd3d783df
checkout:     10d68f507b6b18ff8e721bb7944e5c267dc561e7 2024-11-26 23:53:35 UTC
parent:       317121695e546a07c00b6fedc4658644b430e8bd 2024-11-26 20:15:55 UTC
merged-from:  2f21d351877fd41c49cca45899d8175208318f91 2024-11-25 12:14:54 UTC
tags:         trunk
comment:      Update documentation of the iif() and if() functions. (user: drh)
check-ins:    4580

(5) By Larry Brasfield (larrybr) on 2024-11-28 19:46:26 in reply to 4 [link] [source]

This is still the answer to your question. Do you have reason to disagree?

(6) By userABCD on 2024-11-28 20:13:01 in reply to 5 [link] [source] 

Thank you for the suggestion, but it doesn't answer the question. It provides a way to create a subset of the documents, it doesn't fix the errors, it avoids showing them by omitting the tasks that generate them. That isn't really the same thing.

Our backup system flagged the loss of ~1000 files after the "make fast".

We can't achieve compliance when we have software that produces compilation errors. So we are stuck: use an older version and soon we fall out of compliance with outdated code, or use a newer version and fall out of compliance with an errored compilation.

Is there a third option to use a newer version producing all the files, that doesn't produce the errors?

(7) By Richard Hipp (drh) on 2024-11-28 21:31:18 in reply to 6 [link] [source]

Is there a third option to use a newer version producing all the files, that doesn't produce the errors?

No.

(9) By userABCD on 2024-11-30 15:00:08 in reply to 7 [link] [source] 

Thank you for the concise answer.

One of the other replies mentions a test suite. Is that a separate download?

How can I update the evidence and make it current?

Is there a command like "make update_evidence" or "./refresh_evidence"?

(8) By Larry Brasfield (larrybr) on 2024-11-29 00:58:22 in reply to 6 [link] [source]

The "problems" that you report are not going to be solved with any sleight-of-hand if you insist upon using "make all".

Your desire to make "all the files" will need adjustment. If you were to examine those ~1000 files that vanished with "make fast", you would find that they have no utility for any normal users of SQLite.

Likewise, the "compliance" you speak of will need to be adjusted.

To be blunt: You are attempting to solve the wrong problem. Among the doc system build products, which will actually benefit your customers? You "compliance" criteria should reflect the answer.

(10) By Kees Nuyt (knu) on 2024-11-30 16:23:21 in reply to 6 [link] [source]

We can't achieve compliance when we have software that produces compilation errors.

  • Documentation is just that, documentation.
  • Up to now, sqlitedoc has never been without errors in spelling and grammar
  • The documentation compiles with exit code 0, there are no errors
  • You don't have to compile the documentation, it is always online
  • The software itself (the sqlite library and CLI) compiles without errors, so you are compliant
  • This does not mean it does not contain any bugs: all non-trivial software has bugs, but is still declared compliant. If not, there is not one software package or operating system your organization can use. Back to pencil and paper.
  • High quality software is characterized by bugs being detected regularly and fixed promptly. SQLite complies.
  • If your organization becomes a member of the consortium, you may have some influence on priorities

Just my two cents

(11) By Richard Hipp (drh) on 2024-11-30 18:45:40 in reply to 10 [link] [source]

If your organization becomes a member of the consortium, you may have some influence on priorities

Indeed. Kees does not speak for the developers, but he is spot on here. If you are a consortium member, your concerns about documentation will be addressed promptly and maintained moving forward. We can also come up with other pay-to-play options for you, if you contact us directly.

The "evidence marks" are not something that we are interested in maintaining moving forward. If you want to try to make your own patches to bring them up to date, you are welcomed to do so. Or you can contract with us to do that for you. But it is not likely to be something that happens for "free" because it the developers see no value in it.