database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-31 17:02:12 +03:00
Code Activity

Convert documentation to DocBook XML

Browse Source 
Since some preparation work had already been done, the only source
changes left were changing empty-element tags like <xref linkend="foo">
to <xref linkend="foo"/>, and changing the DOCTYPE.

The source files are still named *.sgml, but they are actually XML files
now.  Renaming could be considered later.

In the build system, the intermediate step to convert from SGML to XML
is removed.  Everything is build straight from the source files again.
The OpenSP (or the old SP) package is no longer needed.

The documentation toolchain instructions are updated and are much
simpler now.

Peter Eisentraut, Alexander Lakhin, Jürgen Purtz
This commit is contained in:
Peter Eisentraut
2017-11-23 09:39:47 -05:00
parent 2f8d6369e6
commit 3c49c6facb
346 changed files with 4260 additions and 4588 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/src/sgml/trigger.sgml
View File

@@ -11,10 +11,10 @@
This chapter provides general information about writing trigger functions.
Trigger functions can be written in most of the available procedural
languages, including
<application>PL/pgSQL</application> (<xref linkend="plpgsql">),
<application>PL/Tcl</application> (<xref linkend="pltcl">),
<application>PL/Perl</application> (<xref linkend="plperl">), and
<application>PL/Python</application> (<xref linkend="plpython">).
<application>PL/pgSQL</application> (<xref linkend="plpgsql"/>),
<application>PL/Tcl</application> (<xref linkend="pltcl"/>),
<application>PL/Perl</application> (<xref linkend="plperl"/>), and
<application>PL/Python</application> (<xref linkend="plpython"/>).
After reading this chapter, you should consult the chapter for
your favorite procedural language to find out the language-specific
details of writing a trigger in it.
@@ -76,7 +76,7 @@
<para>
Once a suitable trigger function has been created, the trigger is
established with
<xref linkend="sql-createtrigger">.
<xref linkend="sql-createtrigger"/>.
The same trigger function can be used for multiple triggers.
</para>
@@ -397,8 +397,8 @@
<para>
Further information about data visibility rules can be found in
<xref linkend="spi-visibility">. The example in <xref
linkend="trigger-example"> contains a demonstration of these rules.
<xref linkend="spi-visibility"/>. The example in <xref
linkend="trigger-example"/> contains a demonstration of these rules.
</para>
</sect1>
@@ -715,7 +715,7 @@ typedef struct Trigger
<para>
To allow queries issued through SPI to reference transition tables, see
<xref linkend="spi-spi-register-trigger-data">.
<xref linkend="spi-spi-register-trigger-data"/>.
</para>
<para>
@@ -835,7 +835,7 @@ trigf(PG_FUNCTION_ARGS)
<para>
After you have compiled the source code (see <xref
linkend="dfunc">), declare the function and the triggers:
linkend="dfunc"/>), declare the function and the triggers:
<programlisting>
CREATE FUNCTION trigf() RETURNS trigger
AS '<replaceable>filename</replaceable>'
@@ -921,7 +921,7 @@ DELETE 2
<para>
There are more complex examples in
<filename>src/test/regress/regress.c</filename> and
in <xref linkend="contrib-spi">.
in <xref linkend="contrib-spi"/>.
</para>
</sect1>
</chapter>