11<!--
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 $
33PostgreSQL documentation
44-->
55
@@ -208,20 +208,19 @@ CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTE
208208 <para>
209209 The <command>CREATE TRIGGER</command> statement in
210210 <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:
213212
214213 <itemizedlist>
215214 <listitem>
216215 <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
218217 (e.g., <literal>AFTER UPDATE OF col1, col2</literal>).
219218 </para>
220219 </listitem>
221220
222221 <listitem>
223222 <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>
225224 and <quote>new</quote> rows or tables for use in the definition
226225 of the triggered action (e.g., <literal>CREATE TRIGGER ... ON
227226 tablename REFERENCING OLD ROW AS somename NEW ROW AS othername
@@ -235,7 +234,7 @@ CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTE
235234 <listitem>
236235 <para>
237236 <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
239238 allows the execution of a number of other SQL commands, such as
240239 <command>CREATE TABLE</command> as triggered action. This
241240 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
246245 </para>
247246
248247 <para>
249- SQL:1999 specifies that multiple triggers should be fired in
248+ SQL:2003 specifies that multiple triggers should be fired in
250249 time-of-creation order. <productname>PostgreSQL</productname> uses
251250 name order, which was judged more convenient to work with.
252251 </para>