/ Check-in [14139542]
Login

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

Overview
Comment:Changes to comments in sqlite3ota.h.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | ota-update
Files: files | file ages | folders
SHA1:14139542b68fbf01632a1b149cd6fca4bb01efa6
User & Date: dan 2014-11-21 11:22:11
Context
2014-11-21
14:37
Merge latest trunk changes with this branch. check-in: 7ef44c5b user: dan tags: ota-update
11:22
Changes to comments in sqlite3ota.h. check-in: 14139542 user: dan tags: ota-update
10:46
Add support for updating virtual tables via ota. check-in: 4dfcfe54 user: dan tags: ota-update
Changes
Hide Diffs Unified Diffs Show Whitespace Changes Patch

Changes to ext/ota/sqlite3ota.h.

57
58
59
60
61
62
63

64
65
66
67
68
69
70
71
72
73
74
75
** An "OTA update" transaction is subject to the following limitations:
**
**   * The transaction must consist of INSERT, UPDATE and DELETE operations
**     only.
**
**   * INSERT statements may not use any default values.
**

**   * UPDATE and DELETE statements must identify their target rows by
**     real PRIMARY KEY values - i.e. INTEGER PRIMARY KEY columns or 
**     by the PRIMARY KEY columns of WITHOUT ROWID tables.
**
**   * UPDATE statements may not modify real PRIMARY KEY columns.
**
**   * No triggers will be fired.
**
**   * No foreign key violations are detected or reported.
**
**   * No constraint handling mode except for "OR ROLLBACK" is supported.
**







>
|
<
|

|







57
58
59
60
61
62
63
64
65

66
67
68
69
70
71
72
73
74
75
** An "OTA update" transaction is subject to the following limitations:
**
**   * The transaction must consist of INSERT, UPDATE and DELETE operations
**     only.
**
**   * INSERT statements may not use any default values.
**
**   * Non-virtual tables that do not have declared primary keys may not 
**     be updated. UPDATE and DELETE statements must identify their target 

**     rows by PRIMARY KEY values. 
**
**   * UPDATE statements may not modify PRIMARY KEY columns.
**
**   * No triggers will be fired.
**
**   * No foreign key violations are detected or reported.
**
**   * No constraint handling mode except for "OR ROLLBACK" is supported.
**