/ Check-in [2e7c1e0a]
Login

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

Overview
Comment:Clarify that OTA is unable to update or delete rows with NULL values in primary key fields.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | ota-update
Files: files | file ages | folders
SHA1:2e7c1e0a0d128d9bac119692b2505b5ed0abe87a
User & Date: dan 2015-03-18 19:04:40
Context
2015-03-18
20:03
Allow whereShortCut() to use the PRIMARY KEY index of a WITHOUT ROWID table to optimize a vector of "IS" operators in a WHERE clause. check-in: 52e73eec user: dan tags: ota-update
19:04
Clarify that OTA is unable to update or delete rows with NULL values in primary key fields. check-in: 2e7c1e0a user: dan tags: ota-update
2015-03-09
13:24
Merge recent trunk enhancements into the ota-update branch. check-in: 5489cb68 user: drh tags: ota-update
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to ext/ota/sqlite3ota.h.

58
59
60
61
62
63
64

65
66
67
68
69
70
71
72
73
**
**   * 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 

**     PRIMARY KEY values. If the table being written has no PRIMARY KEY,
**     affected rows must be identified by rowid.
**
**   * UPDATE statements may not modify PRIMARY KEY columns.
**
**   * No triggers will be fired.
**
**   * No foreign key violations are detected or reported.
**







>
|
|







58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
**
**   * 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 
**     non-NULL PRIMARY KEY values. Rows with NULL values stored in PRIMARY
**     KEY fields may not be updated or deleted. If the table being written 
**     has no PRIMARY KEY, affected rows must be identified by rowid.
**
**   * UPDATE statements may not modify PRIMARY KEY columns.
**
**   * No triggers will be fired.
**
**   * No foreign key violations are detected or reported.
**