1
1
<!--
2
- $PostgreSQL: pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.40 2004/11/27 21:27:07 petere Exp $
2
+ $PostgreSQL: pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.41 2005/07/14 06:17:36 neilc Exp $
3
3
PostgreSQL documentation
4
4
-->
5
5
@@ -208,20 +208,19 @@ CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTE
208
208
<para>
209
209
The <command>CREATE TRIGGER</command> statement in
210
210
<productname>PostgreSQL</productname> implements a subset of the
211
- SQL:1999 standard. (There are no provisions for triggers in SQL-92.)
212
- The following functionality is missing:
211
+ SQL:2003 standard. The following functionality is currently missing:
213
212
214
213
<itemizedlist>
215
214
<listitem>
216
215
<para>
217
- SQL:1999 allows triggers to fire on updates to specific columns
216
+ SQL:2003 allows triggers to fire on updates to specific columns
218
217
(e.g., <literal>AFTER UPDATE OF col1, col2</literal>).
219
218
</para>
220
219
</listitem>
221
220
222
221
<listitem>
223
222
<para>
224
- SQL:1999 allows you to define aliases for the <quote>old</quote>
223
+ SQL:2003 allows you to define aliases for the <quote>old</quote>
225
224
and <quote>new</quote> rows or tables for use in the definition
226
225
of the triggered action (e.g., <literal>CREATE TRIGGER ... ON
227
226
tablename REFERENCING OLD ROW AS somename NEW ROW AS othername
@@ -235,7 +234,7 @@ CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTE
235
234
<listitem>
236
235
<para>
237
236
<productname>PostgreSQL</productname> only allows the execution
238
- of a user-defined function for the triggered action. SQL:1999
237
+ of a user-defined function for the triggered action. SQL:2003
239
238
allows the execution of a number of other SQL commands, such as
240
239
<command>CREATE TABLE</command> as triggered action. This
241
240
limitation is not hard to work around by creating a user-defined
@@ -246,7 +245,7 @@ CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTE
246
245
</para>
247
246
248
247
<para>
249
- SQL:1999 specifies that multiple triggers should be fired in
248
+ SQL:2003 specifies that multiple triggers should be fired in
250
249
time-of-creation order. <productname>PostgreSQL</productname> uses
251
250
name order, which was judged more convenient to work with.
252
251
</para>
0 commit comments