Documentation Source Text

Check-in [b50372204c]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix a typo in rbu.in: "us" -> "use".
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: b50372204c98e7618badd3022097e57449b1a64c
User & Date: dan 2016-04-21 13:37:18.933
Context
2016-04-22
12:14
Update the change log for the unix temporary directory search change. (check-in: 982ce9adde user: drh tags: trunk)
2016-04-21
13:37
Fix a typo in rbu.in: "us" -> "use". (check-in: b50372204c user: dan tags: trunk)
02:35
Merge the 3.12.2 changes from the 3.12 branch. Add a change log entry for SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION. (check-in: 6a5cbbb368 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/rbu.in.
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
<li><p>[UPDATE] statements may not modify PRIMARY KEY or rowid values.
    </p></li>
<li><p>RBU updates cannot be applied to any tables that contain a column
       named "rbu_control".</p></li>
<li><p>The RBU update will not fire any triggers.</p></li>
<li><p>The RBU update will not detect or prevent foreign key or
       CHECK constraint violations.</p></li>
<li><p>All RBU updates us the "OR ROLLBACK" constraint handling mechanism.
    </p></li>
<li><p>The target database may not be in [WAL mode].</p></li>
<li><p>No other writes may occur on the target database while the
       RBU update is being applied.  A read-lock is held on the target
       database to prevent this.</p></li>
</ul>








|







61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
<li><p>[UPDATE] statements may not modify PRIMARY KEY or rowid values.
    </p></li>
<li><p>RBU updates cannot be applied to any tables that contain a column
       named "rbu_control".</p></li>
<li><p>The RBU update will not fire any triggers.</p></li>
<li><p>The RBU update will not detect or prevent foreign key or
       CHECK constraint violations.</p></li>
<li><p>All RBU updates use the "OR ROLLBACK" constraint handling mechanism.
    </p></li>
<li><p>The target database may not be in [WAL mode].</p></li>
<li><p>No other writes may occur on the target database while the
       RBU update is being applied.  A read-lock is held on the target
       database to prevent this.</p></li>
</ul>