sqlite/dist/sqlite3.c

215666 **     to a *-oal file. A *-oal file is just like a *-wal file, except
215667 **     that it is named "<database>-oal" instead of "<database>-wal".
215669 **     "<database>-oal", they go on using the original database in
215670 **     rollback mode while the *-oal file is being generated.
215679 **  2) The "<database>-oal" file is moved to the equivalent "<database>-wal"
215702 **  When state is saved, any commit to the *-oal file and the commit to
215712 **  by delete the RBU update database and *-oal file and have the device
216205 **   * Stage 1, in which changes are accumulated in an oal/wal file, and
216246 **   RBU is currently building a *-oal file. The next call to sqlite3rbu_step()
216247 **   may either add further data to the *-oal file, or compute data that will
216251 **   RBU has finished building the *-oal file. The next call to sqlite3rbu_step()
216252 **   will move the *-oal file to the equivalent *-wal path. If the current
216280 ** the system must at one point move the *-oal file to the equivalent *-wal
216439 **   Valid if STAGE==1. The size in bytes of the *-oal file.
216621 **   finish populating the *-oal file. This allows the sqlite3_bp_progress()
216622 **   API to calculate the permyriadage progress of populating the *-oal file
217761 ** stage 1 of the process (while the *-oal file is being built) while
219492 ** on the database file. This proc moves the *-oal file to the *-wal path,
219493 ** then reopens the database file (this time in vanilla, non-oal, WAL mode).
219506   zOal = sqlite3_mprintf("%s-oal", zMove);
219514     /* Move the *-oal file to *-wal. At this point connection p->db is
219519     ** lock is obtained here before the *-oal is moved to *-wal.
220119 ** If there is a "*-oal" file in the file-system corresponding to the
220124   char *zOal = rbuMPrintf(p, "%s-oal", p->zTarget);
220378           /* Open transactions both databases. The *-oal file is opened or
220507     /* Commit the transaction to the *-oal file. */
220741 **     stage (preparing the *-oal file), the following special handling
220752 **     file, the rbu vfs opens the corresponding *-oal file instead.
220764 **     from automatically checkpointing a *-wal (or *-oal) file from within
221391           /* This call is to open a *-wal file. Intead, open the *-oal. */
221475   **      be intercepted (see the rbuVfsOpen() function) and the *-oal