*** 8,14 ****
and ticket #2224.
----
! **Fixed in Version 3.4.2:**
Setting the
{link: /capi3ref.html#sqlite3_soft_heap_limit soft heap limit}
--- 8,23 ----
and ticket #2224.
----
! **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.
!
!
! **Fixed in Version 3.4.2 (2007-08-13):**
Setting the
{link: /capi3ref.html#sqlite3_soft_heap_limit soft heap limit}
Small. Fast. Reliable.
Choose any three.
Choose any three.
|
|