Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo in the ON CONFLICT clause documentation. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
00422609379bb44a985046785c0bd46f |
| User & Date: | drh 2013-04-14 20:55:52 |
Context
|
2013-04-15
| ||
| 13:16 | Update the FTS4 document to describe the two-argument form of fts4aux. (check-in: ba14e1152f user: drh tags: trunk) | |
|
2013-04-14
| ||
| 20:55 | Fix a typo in the ON CONFLICT clause documentation. (check-in: 0042260937 user: drh tags: trunk) | |
|
2013-04-10
| ||
| 15:02 | Do not include sessions APIs in the main API documentation. (check-in: db41739574 user: drh tags: trunk) | |
Changes
Changes to pages/lang.in.
2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 |
<dt><b>REPLACE</b></dt> <dd><p> ^When a UNIQUE constraint violation occurs, the REPLACE algorithm deletes pre-existing rows that are causing the constraint violation prior to inserting or updating the current row and the command continues executing normally. ^If a NOT NULL constraint violation occurs, the REPLACE conflict resolution replaces the NULL value with he default value for that column, or if the column has no default value, then the ABORT algorithm is used. ^If a CHECK constraint violation occurs, the REPLACE conflict resolution algorithm always works like ABORT.</p> <p>^When the REPLACE conflict resolution strategy deletes rows in order to satisfy a constraint, [CREATE TRIGGER | delete triggers] fire if and only if [recursive_triggers pragma | recursive triggers] are enabled.</p> |
| |
2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 |
<dt><b>REPLACE</b></dt>
<dd><p> ^When a UNIQUE constraint violation occurs, the REPLACE algorithm
deletes pre-existing rows that are causing the constraint violation
prior to inserting or updating the current row and the command continues
executing normally.
^If a NOT NULL constraint violation occurs, the REPLACE conflict
resolution replaces the NULL value with
the default value for that column, or if the column has no default
value, then the ABORT algorithm is used.
^If a CHECK constraint violation occurs, the REPLACE conflict resolution
algorithm always works like ABORT.</p>
<p>^When the REPLACE conflict resolution strategy deletes rows in order to
satisfy a constraint, [CREATE TRIGGER | delete triggers] fire if and only if
[recursive_triggers pragma | recursive triggers] are enabled.</p>
|