Home | History | Annotate | Download | only in dist

Lines Matching full:ahead

774 ** persistent [WAL | Write AHead Log] setting.  By default, the auxiliary
775 ** write ahead log and shared memory files used for transaction control
1873 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
6393 ** <li> the destination database is using write-ahead-log journaling
6668 ** CAPI3REF: Write-Ahead Log Commit Hook
6672 ** [write-ahead log] (i.e. whenever a transaction is committed in
6684 ** is the number of pages currently in the write-ahead log file,
6695 ** A single database handle may have at most a single write-ahead log callback
6697 ** previously registered write-ahead log callback. ^Note that the
6715 ** more frames in the [write-ahead log] file. ^Passing zero or
6742 ** [WAL | write-ahead log mode] then this interface is a harmless no-op.