Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
| Comment: | Fix typos on page onconflict.html: SQLITE_CONSTAIT -> SQLITE_CONSTRAINT and "proscribed" -> "specified by". |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
81daf9c3409356fd2b7b93f7bf6a936f |
| User & Date: | dan 2012-08-11 14:35:42 |
|
2012-08-14
| ||
| 17:10 | First attempt at the website alterations for version 3.7.14. (check-in: 1740b434f3 user: drh tags: trunk) | |
|
2012-08-11
| ||
| 14:35 | Fix typos on page onconflict.html: SQLITE_CONSTAIT -> SQLITE_CONSTRAINT and "proscribed" -> "specified by". (check-in: 81daf9c340 user: dan tags: trunk) | |
|
2012-08-07
| ||
| 22:34 | Use the full name of WinRT for the header and change instances of 'for' to have the same case. (check-in: 1626e732e1 user: mistachkin tags: trunk) | |
Changes to pages/lang.in.
2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 |
active (other than the implied transaction that is created on every
command) then the ROLLBACK resolution algorithm works the same as the
ABORT algorithm.</p></dd>
<dt><b>ABORT</b></dt>
<dd><p> ^When an applicable constraint violation occurs, the ABORT
resolution algorithm aborts the current SQL statement
with an SQLITE_CONSTRAIT error and backs out any changes
made by the current SQL statement; but changes caused
by prior SQL statements within the same transaction are preserved and the
transaction remains active.
This is the default behavior and the behavior proscribed the SQL
standard.</p></dd>
<dt><b>FAIL</b></dt>
<dd><p> ^When an applicable constraint violation occurs, the FAIL
resolution algorithm aborts the current SQL statement with an
SQLITE_CONSTRAINT error. ^But the FAIL resolution does not
back out prior changes of the SQL statement that failed nor does
|
| | |
2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 |
active (other than the implied transaction that is created on every command) then the ROLLBACK resolution algorithm works the same as the ABORT algorithm.</p></dd> <dt><b>ABORT</b></dt> <dd><p> ^When an applicable constraint violation occurs, the ABORT resolution algorithm aborts the current SQL statement with an SQLITE_CONSTRAINT error and backs out any changes made by the current SQL statement; but changes caused by prior SQL statements within the same transaction are preserved and the transaction remains active. This is the default behavior and the behavior specified by the SQL standard.</p></dd> <dt><b>FAIL</b></dt> <dd><p> ^When an applicable constraint violation occurs, the FAIL resolution algorithm aborts the current SQL statement with an SQLITE_CONSTRAINT error. ^But the FAIL resolution does not back out prior changes of the SQL statement that failed nor does |