Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typos. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
bf4a56342e9455459a670a44ba8f2515 |
| User & Date: | drh 2020-05-22 12:21:44 |
Context
|
2020-05-22
| ||
| 17:48 | Version 3.32.0 check-in: d816b04a78 user: drh tags: trunk, release, version-3.32.0 | |
| 12:21 | Fix typos. check-in: bf4a56342e user: drh tags: trunk | |
| 12:12 | Add a news item for the 3.32.0 release. Change the release date to today. check-in: 4e9d9494bb user: drh tags: trunk | |
Changes
Changes to pages/lang_transaction.in.
88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 |
^Transactions can be DEFERRED, IMMEDIATE, or EXCLUSIVE.
^The default transaction behavior is DEFERRED.
</p>
<p>
^DEFERRED means that the transaction does not actually
start until the database is first accessed. ^Internally,
the BEGIN DEFERRRED statement merely sets a flag on the database
connection that turns off the automatic commit that would normally
occur when the last statement finishes. This causes the transaction
that is automatically started to persist until an explicit
COMMIT or ROLLBACK or until a rollback is provoked by an error
or an ON CONFLICT ROLLBACK clause. If the first statement after
BEGIN DEFERRED is a SELECT, then a read transaction is started.
Subsequent write statements will upgrade the transaction to a
|
| |
88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 |
^Transactions can be DEFERRED, IMMEDIATE, or EXCLUSIVE. ^The default transaction behavior is DEFERRED. </p> <p> ^DEFERRED means that the transaction does not actually start until the database is first accessed. ^Internally, the BEGIN DEFERRED statement merely sets a flag on the database connection that turns off the automatic commit that would normally occur when the last statement finishes. This causes the transaction that is automatically started to persist until an explicit COMMIT or ROLLBACK or until a rollback is provoked by an error or an ON CONFLICT ROLLBACK clause. If the first statement after BEGIN DEFERRED is a SELECT, then a read transaction is started. Subsequent write statements will upgrade the transaction to a |
Changes to pages/quirks.in.
324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 |
For example: <codeblock> CREATE TRIGGER AFTER INSERT ON tableX BEGIN INSERT INTO tableY(b) VALUES(new.a); END; </codeblock> <p>The trigger created by the previous statement is named "AFTER" and it is a "BEFORE" trigger. The "AFTER" token is used as an identifer instead of as a keyword, as that is the only way to parse the statement. Another example: <codeblock> CREATE TABLE tableZ(INTEGER PRIMARY KEY); </codeblock> <p>The tableZ table has a single column named "INTEGER". That column has no datatype specified, but it is the PRIMARY KEY. |
| |
324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 |
For example:
<codeblock>
CREATE TRIGGER AFTER INSERT ON tableX BEGIN
INSERT INTO tableY(b) VALUES(new.a);
END;
</codeblock>
<p>The trigger created by the previous statement is named "AFTER"
and it is a "BEFORE" trigger. The "AFTER" token is used as an identifier
instead of as a keyword, as that is the only way to parse the statement.
Another example:
<codeblock>
CREATE TABLE tableZ(INTEGER PRIMARY KEY);
</codeblock>
<p>The tableZ table has a single column named "INTEGER". That column
has no datatype specified, but it is the PRIMARY KEY.
|