*** 11,21 **** --- 11,33 ---- **Fixed In Version 3.4.0 (2007-06-15):** + Two unrelated bugs, both of which could cause database corruption, + were fixed in version 3.4.0 + In version 3.3.0 through 3.3.17, if an SQLITE_BUSY error occurs within an explicit transaction and that transaction is not rolled back, the database file can be corrupted. See CorruptionFollowingBusyError for additional information. + + The second problem (ticket #2418) has existed since version 3.1.0, + but it is very difficult to express. The second problem only + arises when auto-vacuum is enabled and a malloc() failures and + rollback occur following a CREATE TABLE or CREATE INDEX statement + that follows in the same transaction with a large UPDATE statement + that overflows the pager cache. The way to avoid hitting this + bug is to not do CREATE TABLE or CREATE INDEX within a transaction, + especially a transaction that has previously run a large UPDATE. **Fixed In Version 3.3.9 (2007-01-04):**