Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix more typos in the foreignkey.html document. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | version-3.8.4.3 |
| Files: | files | file ages | folders |
| SHA1: |
25bc66990ee8979000db59aec4408b3c |
| User & Date: | drh 2014-04-25 20:47:41 |
Context
|
2014-04-26
| ||
| 00:30 | Update althttpd.c client to log SIGPIPE and SIGSEGV in addition to SIGALRM. (check-in: 5a80e1c8e7 user: drh tags: version-3.8.4.3) | |
|
2014-04-25
| ||
| 20:47 | Fix more typos in the foreignkey.html document. (check-in: 25bc66990e user: drh tags: version-3.8.4.3) | |
| 20:46 | Fix more typos in the foreignkey.html document. (check-in: 2de942054f user: drh tags: trunk) | |
| 20:23 | Fix a typo in the foreign key documentation. (check-in: 821750714a user: drh tags: trunk) | |
|
2014-04-22
| ||
| 00:32 | Rename the "sqlite.html" page to "cli.html". Keep an "sqlite.html" page that redirects to "cli.html". (check-in: a6ea023899 user: drh tags: trunk) | |
Changes
Changes to pages/foreignkeys.in.
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
...
896
897
898
899
900
901
902
903
904
905
906
|
<codeblock>
sqlite> PRAGMA foreign_keys = ON;
</codeblock>
<p>
^Foreign key constraints are disabled by default
(for backwards compatibility),
so must be enabled separately for each [database connection]
separately.
(Note, however, that future releases of SQLite might change
so that foreign key constraints enabled by default. Careful
developers will not
make any assumptions about whether or not foreign keys are enabled by
default but will instead enable or disable them as necessary.)
^The application can can also use a [PRAGMA foreign_keys] statement to
determine if foreign keys are currently enabled. ^(The following
command-line session demonstrates this:
<codeblock>
sqlite> PRAGMA foreign_keys;
0
sqlite> PRAGMA foreign_keys = ON;
sqlite> PRAGMA foreign_keys;
................................................................................
<li><p>
<b>Recursion limit on foreign key actions.</b> ^(The
[SQLITE_MAX_TRIGGER_DEPTH] and [SQLITE_LIMIT_TRIGGER_DEPTH]
settings determine the maximum allowable depth of trigger
program recursion. For the purposes of these limits,
[foreign key actions] are considered trigger programs.)^ ^The
[PRAGMA recursive_triggers] setting does not not affect the operation
of foreign key actions. It is not possible to disable recursive foreign
key actions.
</ol>
|
|
<
|
|
|
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
...
895
896
897
898
899
900
901
902
903
904
905
|
<codeblock>
sqlite> PRAGMA foreign_keys = ON;
</codeblock>
<p>
^Foreign key constraints are disabled by default
(for backwards compatibility),
so must be enabled separately for each [database connection].
(Note, however, that future releases of SQLite might change
so that foreign key constraints enabled by default. Careful
developers will not
make any assumptions about whether or not foreign keys are enabled by
default but will instead enable or disable them as necessary.)
^The application can also use a [PRAGMA foreign_keys] statement to
determine if foreign keys are currently enabled. ^(The following
command-line session demonstrates this:
<codeblock>
sqlite> PRAGMA foreign_keys;
0
sqlite> PRAGMA foreign_keys = ON;
sqlite> PRAGMA foreign_keys;
................................................................................
<li><p>
<b>Recursion limit on foreign key actions.</b> ^(The
[SQLITE_MAX_TRIGGER_DEPTH] and [SQLITE_LIMIT_TRIGGER_DEPTH]
settings determine the maximum allowable depth of trigger
program recursion. For the purposes of these limits,
[foreign key actions] are considered trigger programs.)^ ^The
[PRAGMA recursive_triggers] setting does not affect the operation
of foreign key actions. It is not possible to disable recursive foreign
key actions.
</ol>
|