diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-09-16 15:31:26 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-09-16 15:31:37 -0400 |
| commit | 0749ef8e9eceb04dd8c365443d0d994f7ad34c17 (patch) | |
| tree | a2e2b513cf5ac1f906edf43deb92b051f83452c4 /doc/src/sgml/trigger.sgml | |
| parent | 54d4d0ff6cd40638d026c01e46deb102e7951ba6 (diff) | |
Doc: add example of transition table use in a trigger.
I noticed that there were exactly no complete examples of use of
a transition table in a trigger function, and no clear description
of just how you'd do it either. Improve that.
Diffstat (limited to 'doc/src/sgml/trigger.sgml')
| -rw-r--r-- | doc/src/sgml/trigger.sgml | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml index a16256056f0..f5f74af5a17 100644 --- a/doc/src/sgml/trigger.sgml +++ b/doc/src/sgml/trigger.sgml @@ -317,9 +317,11 @@ be created to make the sets of affected rows available to the trigger. <literal>AFTER ROW</> triggers can also request transition tables, so that they can see the total changes in the table as well as the change in - the individual row they are currently being fired for. The syntax for + the individual row they are currently being fired for. The method for examining the transition tables again depends on the programming language - that is being used. + that is being used, but the typical approach is to make the transition + tables act like read-only temporary tables that can be accessed by SQL + commands issued within the trigger function. </para> </sect1> |