Documentation Source Text

Check-in [dd27f660f9]
Login

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

Overview
Comment:Remove stray "(" character from the ON CONFLICT documentation.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:dd27f660f9d05fc7077792aeb021578fd25fd072
User & Date: drh 2011-09-12 18:29:03
Context
2011-09-15
12:43
Update the code footprint numbers in the documentation (now 350KiB fully configured and 200KiB minimum). check-in: 29d8f8e7c5 user: drh tags: trunk
2011-09-12
18:29
Remove stray "(" character from the ON CONFLICT documentation. check-in: dd27f660f9 user: drh tags: trunk
2011-09-05
11:23
Remove all references to the old CVSTrac wiki, which is no longer supported. check-in: 87f524783e user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/lang.in.

2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
back out prior changes of the SQL statement that failed nor does
it end the transaction.
^For example, if an UPDATE
statement encountered a constraint violation on the 100th row that
it attempts to update, then the first 99 row changes are preserved
but changes to rows 100 and beyond never occur.</p></dd>

(<dt><b>IGNORE</b></dt>
<dd><p> ^When an applicable constraint violation occurs, 
the IGNORE resolution algorithm skips the one row that contains
the constraint violation and continues processing subsequent rows
of the SQL statement as if nothing went wrong.
Other rows before and after the row that
contained the constraint violation are inserted or updated
normally. ^No error is returned when the IGNORE conflict resolution







|







2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
back out prior changes of the SQL statement that failed nor does
it end the transaction.
^For example, if an UPDATE
statement encountered a constraint violation on the 100th row that
it attempts to update, then the first 99 row changes are preserved
but changes to rows 100 and beyond never occur.</p></dd>

<dt><b>IGNORE</b></dt>
<dd><p> ^When an applicable constraint violation occurs, 
the IGNORE resolution algorithm skips the one row that contains
the constraint violation and continues processing subsequent rows
of the SQL statement as if nothing went wrong.
Other rows before and after the row that
contained the constraint violation are inserted or updated
normally. ^No error is returned when the IGNORE conflict resolution