mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Document that after triggers that need to see changed rows should not be

Browse Source 
marked stable.
This commit is contained in:
Bruce Momjian 2010-02-25 22:24:00 +00:00
parent 99419d36f2
commit d98039d896
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/ref/create_function.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.90 2010/02/14 01:01:35 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.91 2010/02/25 22:24:00 momjian Exp $
--> -->
<refentry id="SQL-CREATEFUNCTION"> <refentry id="SQL-CREATEFUNCTION">
@ -289,7 +289,9 @@ CREATE [ OR REPLACE ] FUNCTION
return the same result for the same argument values, but that its return the same result for the same argument values, but that its
result could change across SQL statements. This is the appropriate result could change across SQL statements. This is the appropriate
selection for functions whose results depend on database lookups, selection for functions whose results depend on database lookups,
parameter variables (such as the current time zone), etc. Also note parameter variables (such as the current time zone), etc. (It is
inappropriate for <literal>AFTER</> triggers that wish to
query rows modified by the current command.) Also note
that the <function>current_timestamp</> family of functions qualify that the <function>current_timestamp</> family of functions qualify
as stable, since their values do not change within a transaction. as stable, since their values do not change within a transaction.
</para> </para>