*** 11,17 **** **Fixed in Version 3.5.1 (2007-10-04):** If an SQLITE_FULL error occurs within an explicit transaction ! andtht transaction is not rolled back, the database file can be corrupted. See ticket #2686. This is essentially the same bug that was fixed in version 3.4.0 below except that this time it is the SQLITE_FULL error instead of SQLITE_BUSY. --- 11,17 ---- **Fixed in Version 3.5.1 (2007-10-04):** If an SQLITE_FULL error occurs within an explicit transaction ! and the transaction is not rolled back, the database file can be corrupted. See ticket #2686. This is essentially the same bug that was fixed in version 3.4.0 below except that this time it is the SQLITE_FULL error instead of SQLITE_BUSY. *************** *** 111,117 **** **Fixed in Version 3.1.6 (2005-03-16):** ! Database corruption might occur when inserting records ito a table that has approximately 125 columns. Inserts always work when the table has more columns than this. If some of the fields being inserted are large strings or BLOBs, then corruption might occur with fewer --- 111,117 ---- **Fixed in Version 3.1.6 (2005-03-16):** ! Database corruption might occur when inserting records into a table that has approximately 125 columns. Inserts always work when the table has more columns than this. If some of the fields being inserted are large strings or BLOBs, then corruption might occur with fewer