we know the test cannot be FALSE. The test might end up being NULL in which
case it would need to be treated as false. Ticket #461. (CVS 1103)
FossilOrigin-Name: 5aea81488b2d3bcdc009ccf0f0ffcda046e38d79
correctly constructed. New calls to integrity_check are made in the test
suite. These changes are intended to prevent any future problems such
as seen in ticket #334. (CVS 1024)
FossilOrigin-Name: c9734c27074d2039a1896a8c6965c08d03711b13
to fail when using an index on a column containing an empty string. This
fix is an incompatible file-format change. (CVS 681)
FossilOrigin-Name: 20d152fcddb4fa53556a9c93c7a869600a7c5183
The root problem was that the sequence of BTree operations (Delete, Next)
would not always leave the cursor pointing at the first entry after the
entry that was deleted. A consequence of this error was that a DROP TABLE
on a table with indices would not always remove every index associated
with that table from the SQLITE_MASTER table. Subsequent attempts to
open the database will fail when the index for the missing table was
parsed. Changes have also been made to ignore extra indices in the
SQLITE_MASTER table so that a database previously corrupted by this bug
is once again readable. (CVS 316)
FossilOrigin-Name: 8a984667113564f2bac7412165b6ff8b7e3e8f70