Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||Update RBU description comment in the header file. No changes to code.|
|Downloads:||Tarball | ZIP archive | SQL archive|
|Timelines:||family | ancestors | descendants | both | trunk|
|Files:||files | file ages | folders|
|User & Date:||mistachkin 2015-07-24 00:02:15|
|14:17||Modify a few test scripts to avoid leaving the sqlite3Config structure in a non-default state. (check-in: 562687d9 user: dan tags: trunk)|
|00:02||Update RBU description comment in the header file. No changes to code. (check-in: 119883a2 user: mistachkin tags: trunk)|
|20:44||Change the name of the OTA extension to RBU: Resumable Bulk Update. (check-in: 017c5019 user: drh tags: trunk)|
Changes to ext/rbu/sqlite3rbu.h.
43 43 ** guarantee that a single update process will run for long enough to apply 44 44 ** the entire update, for example because the update is being applied on a 45 45 ** mobile device that is frequently rebooted. Even after the writer process 46 46 ** has committed one or more sub-transactions, other database clients continue 47 47 ** to read from the original database snapshot. In other words, partially 48 48 ** applied transactions are not visible to other clients. 49 49 ** 50 -** "RBU" stands for "Over The Air" update. As in a large database update 50 +** "RBU" stands for "Resumable Bulk Update". As in a large database update 51 51 ** transmitted via a wireless network to a mobile device. A transaction 52 52 ** applied using this extension is hence refered to as an "RBU update". 53 53 ** 54 54 ** 55 55 ** LIMITATIONS 56 56 ** 57 57 ** An "RBU update" transaction is subject to the following limitations: