Documentation Source Text

Check-in [e0f55595d4]
Login

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

Overview
Comment:Clarify the rules for referencing tables in triggers.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: e0f55595d4a0da400bcfd1d9bf38a03bf90b1c59685fb497f48ae8b91f70f0ac
User & Date: drh 2017-06-09 12:23:02.717
Context
2017-06-16
11:53
Add change-log, chronology, and news entries for the 3.18.1 release. (check-in: 48b0c119e2 user: drh tags: trunk)
2017-06-09
12:23
Clarify the rules for referencing tables in triggers. (check-in: e0f55595d4 user: drh tags: trunk)
2017-06-08
19:31
Refinements to the faster-than-filesystem article based on peer review. (check-in: e5a09f2ea2 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/lang.in.
1258
1259
1260
1261
1262
1263
1264
1265




1266


1267
1268
1269
1270
1271
1272
1273
restrictions apply:</p>

<ul>
<li><p>
  ^(The name of the table to be modified in an [UPDATE], [DELETE], or [INSERT]
  statement must be an unqualified table name.  In other words, one must
  use just "<i>tablename</i>" not "<i>database</i><b>.</b><i>tablename</i>"
  when specifying the table.)^  ^The table to be modified must exist in the




  same database as the table or view to which the trigger is attached.


  </p></li>

<li><p>
  ^The "INSERT INTO <i>table</i> DEFAULT VALUES" form of the [INSERT] statement
  is not supported.
  </p></li>








|
>
>
>
>

>
>







1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
restrictions apply:</p>

<ul>
<li><p>
  ^(The name of the table to be modified in an [UPDATE], [DELETE], or [INSERT]
  statement must be an unqualified table name.  In other words, one must
  use just "<i>tablename</i>" not "<i>database</i><b>.</b><i>tablename</i>"
  when specifying the table.)^ </p></li>

<li><p>
 ^For non-TEMP triggers,
  the table to be modified or queried must exist in the
  same database as the table or view to which the trigger is attached.
  ^(TEMP triggers are not subject to the same-database rule.  A TEMP
  trigger is allowed to query or modify any table in any [ATTACH]-ed database.)^
  </p></li>

<li><p>
  ^The "INSERT INTO <i>table</i> DEFAULT VALUES" form of the [INSERT] statement
  is not supported.
  </p></li>