<!-- doc/src/sgml/contrib-spi.sgml -->

<sect1 id="contrib-spi" xreflabel="spi">
 <title>spi</title>

 <indexterm zone="contrib-spi">
  <primary>SPI</primary>
  <secondary>examples</secondary>
 </indexterm>

 <para>
  The <application>spi</application> module provides several workable examples
  of using SPI and triggers.  While these functions are of some value in
  their own right, they are even more useful as examples to modify for
  your own purposes.  The functions are general enough to be used
  with any table, but you have to specify table and field names (as described
  below) while creating a trigger.
 </para>

 <para>
  Each of the groups of functions described below is provided as a
  separately-installable extension.
 </para>

 <sect2>
  <title>refint &mdash; Functions for Implementing Referential Integrity</title>

  <para>
   <function>check_primary_key()</function> and
   <function>check_foreign_key()</function> are used to check foreign key constraints.
   (This functionality is long since superseded by the built-in foreign
   key mechanism, of course, but the module is still useful as an example.)
  </para>

  <para>
   <function>check_primary_key()</function> checks the referencing table.
   To use, create a <literal>BEFORE INSERT OR UPDATE</literal> trigger using this
   function on a table referencing another table. Specify as the trigger
   arguments: the referencing table's column name(s) which form the foreign
   key, the referenced table name, and the column names in the referenced table
   which form the primary/unique key.  To handle multiple foreign
   keys, create a trigger for each reference.
  </para>

  <para>
   <function>check_foreign_key()</function> checks the referenced table.
   To use, create a <literal>BEFORE DELETE OR UPDATE</literal> trigger using this
   function on a table referenced by other table(s).  Specify as the trigger
   arguments: the number of referencing tables for which the function has to
   perform checking, the action if a referencing key is found
   (<literal>cascade</literal> &mdash; to delete the referencing row,
   <literal>restrict</literal> &mdash; to abort transaction if referencing keys
   exist, <literal>setnull</literal> &mdash; to set referencing key fields to null),
   the triggered table's column names which form the primary/unique key, then
   the referencing table name and column names (repeated for as many
   referencing tables as were specified by first argument).  Note that the
   primary/unique key columns should be marked NOT NULL and should have a
   unique index.
  </para>

  <para>
   There are examples in <filename>refint.example</filename>.
  </para>
 </sect2>

 <sect2>
  <title>timetravel &mdash; Functions for Implementing Time Travel</title>

  <para>
   Long ago, <productname>PostgreSQL</productname> had a built-in time travel feature
   that kept the insert and delete times for each tuple.  This can be
   emulated using these functions.  To use these functions,
   you must add to a table two columns of <type>abstime</type> type to store
   the date when a tuple was inserted (start_date) and changed/deleted
   (stop_date):

<programlisting>
CREATE TABLE mytab (
        ...             ...
        start_date      abstime,
        stop_date       abstime
        ...             ...
);
</programlisting>

   The columns can be named whatever you like, but in this discussion
   we'll call them start_date and stop_date.
  </para>

  <para>
   When a new row is inserted, start_date should normally be set to
   current time, and stop_date to <literal>infinity</literal>.  The trigger
   will automatically substitute these values if the inserted data
   contains nulls in these columns.  Generally, inserting explicit
   non-null data in these columns should only be done when re-loading
   dumped data.
  </para>

  <para>
   Tuples with stop_date equal to <literal>infinity</literal> are <quote>valid
   now</quote>, and can be modified.  Tuples with a finite stop_date cannot
   be modified anymore &mdash; the trigger will prevent it.  (If you need
   to do that, you can turn off time travel as shown below.)
  </para>

  <para>
   For a modifiable row, on update only the stop_date in the tuple being
   updated will be changed (to current time) and a new tuple with the modified
   data will be inserted.  Start_date in this new tuple will be set to current
   time and stop_date to <literal>infinity</literal>.
  </para>

  <para>
   A delete does not actually remove the tuple but only sets its stop_date
   to current time.
  </para>

  <para>
   To query for tuples <quote>valid now</quote>, include
   <literal>stop_date = 'infinity'</literal> in the query's WHERE condition.
   (You might wish to incorporate that in a view.)  Similarly, you can
   query for tuples valid at any past time with suitable conditions on
   start_date and stop_date.
  </para>

  <para>
   <function>timetravel()</function> is the general trigger function that supports
   this behavior.  Create a <literal>BEFORE INSERT OR UPDATE OR DELETE</literal>
   trigger using this function on each time-traveled table. Specify two
   trigger arguments: the actual
   names of the start_date and stop_date columns.
   Optionally, you can specify one to three more arguments, which must refer
   to columns of type <type>text</type>.  The trigger will store the name of
   the current user into the first of these columns during INSERT, the
   second column during UPDATE, and the third during DELETE.
  </para>

  <para>
   <function>set_timetravel()</function> allows you to turn time-travel on or off for
   a table.
   <literal>set_timetravel('mytab', 1)</literal> will turn TT ON for table <literal>mytab</literal>.
   <literal>set_timetravel('mytab', 0)</literal> will turn TT OFF for table <literal>mytab</literal>.
   In both cases the old status is reported.  While TT is off, you can modify
   the start_date and stop_date columns freely.  Note that the on/off status
   is local to the current database session &mdash; fresh sessions will
   always start out with TT ON for all tables.
  </para>

  <para>
   <function>get_timetravel()</function> returns the TT state for a table without
   changing it.
  </para>

  <para>
   There is an example in <filename>timetravel.example</filename>.
  </para>
 </sect2>

 <sect2>
  <title>autoinc &mdash; Functions for Autoincrementing Fields</title>

  <para>
   <function>autoinc()</function> is a trigger that stores the next value of
   a sequence into an integer field.  This has some overlap with the
   built-in <quote>serial column</quote> feature, but it is not the same:
   <function>autoinc()</function> will override attempts to substitute a
   different field value during inserts, and optionally it can be
   used to increment the field during updates, too.
  </para>

  <para>
   To use, create a <literal>BEFORE INSERT</literal> (or optionally <literal>BEFORE
   INSERT OR UPDATE</literal>) trigger using this function.  Specify two
   trigger arguments: the name of the integer column to be modified,
   and the name of the sequence object that will supply values.
   (Actually, you can specify any number of pairs of such names, if
   you'd like to update more than one autoincrementing column.)
  </para>

  <para>
   There is an example in <filename>autoinc.example</filename>.
  </para>

 </sect2>

 <sect2>
  <title>insert_username &mdash; Functions for Tracking Who Changed a Table</title>

  <para>
   <function>insert_username()</function> is a trigger that stores the current
   user's name into a text field.  This can be useful for tracking
   who last modified a particular row within a table.
  </para>

  <para>
   To use, create a <literal>BEFORE INSERT</literal> and/or <literal>UPDATE</literal>
   trigger using this function.  Specify a single trigger
   argument: the name of the text column to be modified.
  </para>

  <para>
   There is an example in <filename>insert_username.example</filename>.
  </para>

 </sect2>

 <sect2>
  <title>moddatetime &mdash; Functions for Tracking Last Modification Time</title>

  <para>
   <function>moddatetime()</function> is a trigger that stores the current
   time into a <type>timestamp</type> field.  This can be useful for tracking
   the last modification time of a particular row within a table.
  </para>

  <para>
   To use, create a <literal>BEFORE UPDATE</literal>
   trigger using this function.  Specify a single trigger
   argument: the name of the column to be modified.
   The column must be of type <type>timestamp</type> or <type>timestamp with
   time zone</type>.
  </para>

  <para>
   There is an example in <filename>moddatetime.example</filename>.
  </para>

 </sect2>

</sect1>
