Cherrypick the changes for enhancement requests [e090183531fc27474]
(use indices on LIKE with no wildcards) and [4711020446da7d93d993]
(use nocase index for LIKE even if the column is binary) into the
3.6.23.1 release of the Apple-OSX branch.
check-in: 220cca50 user: drh tags: apple-osx-3623

If an SQLITE_FULL error occurs during rollback or journal finalization, treat it in the same way as SQLITE_IOERR (i.e. require that the pager internals be completely reset before it is next read from or written to).
check-in: 8ac18523 user: dan tags: trunk

Fix a problem wherein changing the journal-mode immediately after leaving exclusive-locking mode could lead to the database being unlocked without clearing the changeCountDone flag.
check-in: 531abc80 user: dan tags: experimental

Do not run some tests in notify3.test with the inmemory_journal permutation. They do not pass as the tests assume that the database schema is not loaded until the first invocation of [db eval]. This is not true with the inmemory_journal permutation.
check-in: 698fba82 user: dan tags: trunk

Fix the query planner so that when it has a choice of full-scan tables to
move to the outer loop, it chooses the one that is likely to give the fewest
output rows. Ticket [13f033c865f878].
check-in: 309bbedf user: drh tags: trunk

If the outer loop of a join must be a full table scan, make sure that an
incomplete ANALYZE does not trick the planner into use a table that might
be indexable in an inner loop. Ticket [13f033c865f878]check-in: e7a714b5 user: drh tags: trunk

When opening a write-transaction on a database file that has been appended to or truncated by a pre-3.7.0 client, update the database-size field in the database header. Fix for [51ae9cad31].
check-in: 65b8636a user: dan tags: trunk

If a database becomes corrupted such that an index is out of sync with its
table, make sure the corruption is detected and reported back. Do not assume
that indices always contain rowids for valid table rows.
check-in: 83395a3d user: drh tags: trunk

Changes to the comments describing the Pager.setMaster variable in pager.c. Add an assert() statement to verify that two master journal pointers are not written to a single journal file.
check-in: ad78ccac user: dan tags: trunk

Make sure a connection has an exclusive lock on all database files involved in a multi-file transaction before writing the master-journal pointer into any journal files. Fix for [f3e5abed55].
check-in: 50c0f220 user: dan tags: experimental

This page was generated in about
0.008s by
Fossil 2.10 [b94e15cff7] 2019-09-13 13:54:36