Lines Matching refs:hot

22955   ** write operation (not a hot journal rollback).
24380   ** doing a hot-journal rollback or a write to some file other than a
24622     ** doing a hot-journal rollback or a write to some file other than a
32449   ** dangerous because the code to rollback a hot-journal file
32451   ** whether or not the journal is hot. 
32540 ** treated as a hot-journal and rolled back.
32602 ** it were a hot-journal).
32626 ** there is a hot-journal left in the file-system, the next connection
32647 ** after rollback of a hot-journal, or if an error occurs while opening
32658 ** transaction. Nor will it be considered to be a hot-journal by this
32733       ** a hot-journal was just rolled back. In this case the journal
33166 ** or rolling back a transaction (including rolling back a hot-journal).
33288 ** that might be a hot journal.  Or, it could be that the journal is 
33290 ** If the journal really is hot, reset the pager cache prior rolling
33316   ** present on disk, then the journal is not hot and does not need to be
33374     ** When rolling back a hot journal, nRec==0 always means that the next
33700 ** (which occurs during hot-journal rollback). Summary:
34050 ** a hot journal may be left in the filesystem but no error is returned
34109 ** disk and can be restored in the event of a hot-journal rollback.
34162         ** hot-journal rollback following recovery. It may roll back all
34599       ** check for a hot-journal before reading.
34786 ** PAGER_SHARED state. It tests if there is a hot journal present in
34787 ** the file-system for the given pager. A hot journal is one that 
34788 ** needs to be played back. According to this function, a hot-journal
34804 ** does not exist, then the journal file is not really hot. In this
34806 ** routine will discover that the journal file is not really hot and 
34809 ** If a hot-journal file is found to exist, *pExists is set to 1 and 
34810 ** SQLITE_OK returned. If no hot-journal file is present, *pExists is
34812 ** to determine whether or not a hot-journal file exists, the IO error
34835     ** is the case, this routine might think there is a hot journal when
34862           ** If there is, then we consider this journal to be hot. If not, 
34879             ** ticket #3883.  Either way, assume that the journal is hot.
34952 **      the SHARED lock, the file-system is checked for a hot-journal,
34953 **      which is played back if present. Following any hot-journal 
34970 ** IO error occurs while locking the database, checking for a hot-journal
34984   ** any hot journal in the file-system.
35027       ** hot-journal back.
35085       ** playing back the hot-journal so that we don't end up with
35396 ** when opening a hot journal file to roll it back.
36137 ** be used as a hot-journal and the current transaction rolled back.
36141 ** for hot-journal rollback. Once this is done the transaction is
36167   ** a hot-journal during hot-journal rollback, 0 changes will be made
36193 **   2) It finalizes the journal file, so that it is not used for hot
36226 **   hot-journal rollback).