mirror of
https://github.com/postgres/postgres.git
synced 2025-09-03 15:22:11 +03:00
Make an editorial pass over the reference pages.
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.41 2005/07/14 06:17:36 neilc Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.42 2005/11/01 21:09:50 tgl Exp $
|
||||
PostgreSQL documentation
|
||||
-->
|
||||
|
||||
@@ -208,19 +208,19 @@ CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTE
|
||||
<para>
|
||||
The <command>CREATE TRIGGER</command> statement in
|
||||
<productname>PostgreSQL</productname> implements a subset of the
|
||||
SQL:2003 standard. The following functionality is currently missing:
|
||||
<acronym>SQL</> standard. The following functionality is currently missing:
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
SQL:2003 allows triggers to fire on updates to specific columns
|
||||
SQL allows triggers to fire on updates to specific columns
|
||||
(e.g., <literal>AFTER UPDATE OF col1, col2</literal>).
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
SQL:2003 allows you to define aliases for the <quote>old</quote>
|
||||
SQL allows you to define aliases for the <quote>old</quote>
|
||||
and <quote>new</quote> rows or tables for use in the definition
|
||||
of the triggered action (e.g., <literal>CREATE TRIGGER ... ON
|
||||
tablename REFERENCING OLD ROW AS somename NEW ROW AS othername
|
||||
@@ -234,9 +234,9 @@ CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTE
|
||||
<listitem>
|
||||
<para>
|
||||
<productname>PostgreSQL</productname> only allows the execution
|
||||
of a user-defined function for the triggered action. SQL:2003
|
||||
of a user-defined function for the triggered action. The standard
|
||||
allows the execution of a number of other SQL commands, such as
|
||||
<command>CREATE TABLE</command> as triggered action. This
|
||||
<command>CREATE TABLE</command> as the triggered action. This
|
||||
limitation is not hard to work around by creating a user-defined
|
||||
function that executes the desired commands.
|
||||
</para>
|
||||
@@ -245,7 +245,7 @@ CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTE
|
||||
</para>
|
||||
|
||||
<para>
|
||||
SQL:2003 specifies that multiple triggers should be fired in
|
||||
SQL specifies that multiple triggers should be fired in
|
||||
time-of-creation order. <productname>PostgreSQL</productname> uses
|
||||
name order, which was judged more convenient to work with.
|
||||
</para>
|
||||
|
Reference in New Issue
Block a user