Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix a typo in the session documentation. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
acfc24126f17be971f10ed0d15d47c48 |
User & Date: | drh 2017-06-02 11:27:15.918 |
Context
2017-06-05
| ||
11:04 | Change references to www.hwaci.com to use HTTPS instead of HTTP (check-in: 43205871ea user: drh tags: trunk) | |
2017-06-02
| ||
11:27 | Fix a typo in the session documentation. (check-in: acfc24126f user: drh tags: trunk) | |
11:24 | Remove an incorrect statement about sessions and WITHOUT ROWID from the WITHOUT ROWID documentation. (check-in: 65df8fdcfa user: drh tags: trunk) | |
Changes
Changes to pages/sessionintro.in.
︙ | ︙ | |||
134 135 136 137 138 139 140 | <li><p> For an <b>UPDATE</b> change, the payload consists of the PRIMARY KEY fields and the new values of modified fields only. The original values of modified fields are not stored as part of a patchset. </ul> <h2>Conflicts</h2> | | | 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 | <li><p> For an <b>UPDATE</b> change, the payload consists of the PRIMARY KEY fields and the new values of modified fields only. The original values of modified fields are not stored as part of a patchset. </ul> <h2>Conflicts</h2> <p> When a changeset or patchset is applied to a database, an attempt is made to insert a new row for each INSERT change, remove a row for each DELETE change and modify a row for each UPDATE change. If the target database is in the same state as the original database that the changeset was recorded on, this is a simple matter. However, if the contents of the target database is not in exactly this state, conflicts can occur when applying the changeset or patchset. |
︙ | ︙ |