Sophie: postgresql8.2-docs-8.2.14-1mdv2010.0 i586

postgresql8.2-docs-8.2.14-1mdv2010.0.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>CREATE FUNCTION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 8.2.14 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="SQL Commands"
HREF="sql-commands.html"><LINK
REL="PREVIOUS"
TITLE="CREATE DOMAIN"
HREF="sql-createdomain.html"><LINK
REL="NEXT"
TITLE="CREATE GROUP"
HREF="sql-creategroup.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2009-09-04T05:25:47"></HEAD
><BODY
CLASS="REFENTRY"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
>PostgreSQL 8.2.14 Documentation</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-createdomain.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-createdomain.html"
>Fast Backward</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="sql-creategroup.html"
>Fast Forward</A
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="sql-creategroup.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
><A
NAME="SQL-CREATEFUNCTION"
></A
>CREATE FUNCTION</H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN47164"
></A
><H2
>Name</H2
>CREATE FUNCTION&nbsp;--&nbsp;define a new function</DIV
><A
NAME="AEN47167"
></A
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN47169"
></A
><H2
>Synopsis</H2
><PRE
CLASS="SYNOPSIS"
>CREATE [ OR REPLACE ] FUNCTION
    <TT
CLASS="REPLACEABLE"
><I
>name</I
></TT
> ( [ [ <TT
CLASS="REPLACEABLE"
><I
>argmode</I
></TT
> ] [ <TT
CLASS="REPLACEABLE"
><I
>argname</I
></TT
> ] <TT
CLASS="REPLACEABLE"
><I
>argtype</I
></TT
> [, ...] ] )
    [ RETURNS <TT
CLASS="REPLACEABLE"
><I
>rettype</I
></TT
> ]
  { LANGUAGE <TT
CLASS="REPLACEABLE"
><I
>langname</I
></TT
>
    | IMMUTABLE | STABLE | VOLATILE
    | CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT
    | [ EXTERNAL ] SECURITY INVOKER | [ EXTERNAL ] SECURITY DEFINER
    | AS '<TT
CLASS="REPLACEABLE"
><I
>definition</I
></TT
>'
    | AS '<TT
CLASS="REPLACEABLE"
><I
>obj_file</I
></TT
>', '<TT
CLASS="REPLACEABLE"
><I
>link_symbol</I
></TT
>'
  } ...
    [ WITH ( <TT
CLASS="REPLACEABLE"
><I
>attribute</I
></TT
> [, ...] ) ]</PRE
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="SQL-CREATEFUNCTION-DESCRIPTION"
></A
><H2
>Description</H2
><P
>   <TT
CLASS="COMMAND"
>CREATE FUNCTION</TT
> defines a new function.
   <TT
CLASS="COMMAND"
>CREATE OR REPLACE FUNCTION</TT
> will either create a
   new function, or replace an existing definition.
  </P
><P
>   If a schema name is included, then the function is created in the
   specified schema.  Otherwise it is created in the current schema.
   The name of the new function must not match any existing function
   with the same argument types in the same schema.  However,
   functions of different argument types may share a name (this is
   called <I
CLASS="FIRSTTERM"
>overloading</I
>).
  </P
><P
>   To update the definition of an existing function, use
   <TT
CLASS="COMMAND"
>CREATE OR REPLACE FUNCTION</TT
>.  It is not possible
   to change the name or argument types of a function this way (if you
   tried, you would actually be creating a new, distinct function).
   Also, <TT
CLASS="COMMAND"
>CREATE OR REPLACE FUNCTION</TT
> will not let
   you change the return type of an existing function.  To do that,
   you must drop and recreate the function.  (When using <TT
CLASS="LITERAL"
>OUT</TT
>
   parameters, that means you can't change the names or types of any
   <TT
CLASS="LITERAL"
>OUT</TT
> parameters except by dropping the function.)
  </P
><P
>   If you drop and then recreate a function, the new function is not
   the same entity as the old; you will have to drop existing rules, views,
   triggers, etc. that refer to the old function.  Use
   <TT
CLASS="COMMAND"
>CREATE OR REPLACE FUNCTION</TT
> to change a function
   definition without breaking objects that refer to the function.
  </P
><P
>   The user that creates the function becomes the owner of the function.
  </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN47196"
></A
><H2
>Parameters</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="REPLACEABLE"
><I
>name</I
></TT
></DT
><DD
><P
>       The name (optionally schema-qualified) of the function to create.
      </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>argmode</I
></TT
></DT
><DD
><P
>       The mode of an argument: either <TT
CLASS="LITERAL"
>IN</TT
>, <TT
CLASS="LITERAL"
>OUT</TT
>,
       or <TT
CLASS="LITERAL"
>INOUT</TT
>.  If omitted, the default is <TT
CLASS="LITERAL"
>IN</TT
>.
      </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>argname</I
></TT
></DT
><DD
><P
>       The name of an argument. Some languages (currently only PL/pgSQL) let
       you use the name in the function body.  For other languages the
       name of an input argument is just extra documentation.  But the name
       of an output argument is significant, since it defines the column
       name in the result row type.  (If you omit the name for an output
       argument, the system will choose a default column name.)
      </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>argtype</I
></TT
></DT
><DD
><P
>       The data type(s) of the function's arguments (optionally 
       schema-qualified), if any. The argument types may be base, composite,
       or domain types, or may reference the type of a table column.
      </P
><P
>       Depending on the implementation language it may also be allowed
       to specify <SPAN
CLASS="QUOTE"
>"pseudotypes"</SPAN
> such as <TT
CLASS="TYPE"
>cstring</TT
>.
       Pseudotypes indicate that the actual argument type is either
       incompletely specified, or outside the set of ordinary SQL data types.
      </P
><P
>       The type of a column is referenced by writing
       <TT
CLASS="LITERAL"
><TT
CLASS="REPLACEABLE"
><I
>tablename</I
></TT
>.<TT
CLASS="REPLACEABLE"
><I
>columnname</I
></TT
>%TYPE</TT
>.
       Using this feature can sometimes help make a function independent of
       changes to the definition of a table.
      </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>rettype</I
></TT
></DT
><DD
><P
>       The return data type (optionally schema-qualified). The return type 
       may be a base, composite, or domain type,
       or may reference the type of a table column.
       Depending on the implementation language it may also be allowed
       to specify <SPAN
CLASS="QUOTE"
>"pseudotypes"</SPAN
> such as <TT
CLASS="TYPE"
>cstring</TT
>.
       If the function is not supposed to return a value, specify
       <TT
CLASS="TYPE"
>void</TT
> as the return type.
      </P
><P
>       When there are <TT
CLASS="LITERAL"
>OUT</TT
> or <TT
CLASS="LITERAL"
>INOUT</TT
> parameters,
       the <TT
CLASS="LITERAL"
>RETURNS</TT
> clause may be omitted.  If present, it
       must agree with the result type implied by the output parameters:
       <TT
CLASS="LITERAL"
>RECORD</TT
> if there are multiple output parameters, or
       the same type as the single output parameter.
      </P
><P
>       The <TT
CLASS="LITERAL"
>SETOF</TT
>
       modifier indicates that the function will return a set of
       items, rather than a single item.
      </P
><P
>       The type of a column is referenced by writing
       <TT
CLASS="LITERAL"
><TT
CLASS="REPLACEABLE"
><I
>tablename</I
></TT
>.<TT
CLASS="REPLACEABLE"
><I
>columnname</I
></TT
>%TYPE</TT
>.
      </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>langname</I
></TT
></DT
><DD
><P
>       The name of the language that the function is implemented in.
       May be <TT
CLASS="LITERAL"
>SQL</TT
>, <TT
CLASS="LITERAL"
>C</TT
>,
       <TT
CLASS="LITERAL"
>internal</TT
>, or the name of a user-defined
       procedural language.  For backward compatibility,
       the name may be enclosed by single quotes.
      </P
></DD
><DT
><TT
CLASS="LITERAL"
>IMMUTABLE</TT
><BR><TT
CLASS="LITERAL"
>STABLE</TT
><BR><TT
CLASS="LITERAL"
>VOLATILE</TT
></DT
><DD
><P
>       These attributes inform the query optimizer about the behavior
       of the function.  At most one choice
       may be specified.  If none of these appear,
       <TT
CLASS="LITERAL"
>VOLATILE</TT
> is the default assumption.
      </P
><P
>       <TT
CLASS="LITERAL"
>IMMUTABLE</TT
> indicates that the function
       cannot modify the database and always
       returns the same result when given the same argument values; that
       is, it does not do database lookups or otherwise use information not
       directly present in its argument list.  If this option is given,
       any call of the function with all-constant arguments can be
       immediately replaced with the function value.
      </P
><P
>       <TT
CLASS="LITERAL"
>STABLE</TT
> indicates that the function
       cannot modify the database,
       and that within a single table scan it will consistently
       return the same result for the same argument values, but that its
       result could change across SQL statements.  This is the appropriate
       selection for functions whose results depend on database lookups,
       parameter variables (such as the current time zone), etc.  Also note
       that the <CODE
CLASS="FUNCTION"
>current_timestamp</CODE
> family of functions qualify
       as stable, since their values do not change within a transaction.
      </P
><P
>       <TT
CLASS="LITERAL"
>VOLATILE</TT
> indicates that the function value can
       change even within a single table scan, so no optimizations can be
       made.  Relatively few database functions are volatile in this sense;
       some examples are <TT
CLASS="LITERAL"
>random()</TT
>, <TT
CLASS="LITERAL"
>currval()</TT
>,
       <TT
CLASS="LITERAL"
>timeofday()</TT
>.  But note that any function that has
       side-effects must be classified volatile, even if its result is quite
       predictable, to prevent calls from being optimized away; an example is
       <TT
CLASS="LITERAL"
>setval()</TT
>.
      </P
><P
>       For additional details see <A
HREF="xfunc-volatility.html"
>Section 33.6</A
>.
      </P
></DD
><DT
><TT
CLASS="LITERAL"
>CALLED ON NULL INPUT</TT
><BR><TT
CLASS="LITERAL"
>RETURNS NULL ON NULL INPUT</TT
><BR><TT
CLASS="LITERAL"
>STRICT</TT
></DT
><DD
><P
>       <TT
CLASS="LITERAL"
>CALLED ON NULL INPUT</TT
> (the default) indicates
       that the function will be called normally when some of its
       arguments are null.  It is then the function author's
       responsibility to check for null values if necessary and respond
       appropriately.
      </P
><P
>       <TT
CLASS="LITERAL"
>RETURNS NULL ON NULL INPUT</TT
> or
       <TT
CLASS="LITERAL"
>STRICT</TT
> indicates that the function always
       returns null whenever any of its arguments are null.  If this
       parameter is specified, the function is not executed when there
       are null arguments; instead a null result is assumed
       automatically.
      </P
></DD
><DT
><TT
CLASS="LITERAL"
>[<SPAN
CLASS="OPTIONAL"
>EXTERNAL</SPAN
>] SECURITY INVOKER</TT
><BR><TT
CLASS="LITERAL"
>[<SPAN
CLASS="OPTIONAL"
>EXTERNAL</SPAN
>] SECURITY DEFINER</TT
></DT
><DD
><P
>      <TT
CLASS="LITERAL"
>SECURITY INVOKER</TT
> indicates that the function
      is to be executed with the privileges of the user that calls it.
      That is the default.  <TT
CLASS="LITERAL"
>SECURITY DEFINER</TT
>
      specifies that the function is to be executed with the
      privileges of the user that created it.
     </P
><P
>      The key word <TT
CLASS="LITERAL"
>EXTERNAL</TT
> is allowed for SQL
      conformance, but it is optional since, unlike in SQL, this feature
      applies to all functions not only external ones.
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>definition</I
></TT
></DT
><DD
><P
>       A string constant defining the function; the meaning depends on the
       language.  It may be an internal function name, the path to an
       object file, an SQL command, or text in a procedural language.
      </P
></DD
><DT
><TT
CLASS="LITERAL"
><TT
CLASS="REPLACEABLE"
><I
>obj_file</I
></TT
>, <TT
CLASS="REPLACEABLE"
><I
>link_symbol</I
></TT
></TT
></DT
><DD
><P
>       This form of the <TT
CLASS="LITERAL"
>AS</TT
> clause is used for
       dynamically loadable C language functions when the function name
       in the C language source code is not the same as the name of
       the SQL function. The string <TT
CLASS="REPLACEABLE"
><I
>obj_file</I
></TT
> is the name of the
       file containing the dynamically loadable object, and
       <TT
CLASS="REPLACEABLE"
><I
>link_symbol</I
></TT
> is the
       function's link symbol, that is, the name of the function in the C
       language source code.  If the link symbol is omitted, it is assumed
       to be the same as the name of the SQL function being defined.
      </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>attribute</I
></TT
></DT
><DD
><P
>       The historical way to specify optional pieces of information
       about the function.  The following attributes may appear here:

      <P
></P
></P><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="LITERAL"
>isStrict</TT
></DT
><DD
><P
>          Equivalent to <TT
CLASS="LITERAL"
>STRICT</TT
> or <TT
CLASS="LITERAL"
>RETURNS NULL ON NULL INPUT</TT
>.
         </P
></DD
><DT
><TT
CLASS="LITERAL"
>isCachable</TT
></DT
><DD
><P
>          <TT
CLASS="LITERAL"
>isCachable</TT
> is an obsolete equivalent of
          <TT
CLASS="LITERAL"
>IMMUTABLE</TT
>; it's still accepted for
          backwards-compatibility reasons.
         </P
></DD
></DL
></DIV
><P>

      Attribute names are not case-sensitive.
     </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="SQL-CREATEFUNCTION-NOTES"
></A
><H2
>Notes</H2
><P
>    Refer to <A
HREF="xfunc.html"
>Section 33.3</A
> for further information on writing
    functions.
   </P
><P
>    The full <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> type syntax is allowed for
    input arguments and return value. However, some details of the
    type specification (e.g., the precision field for
    type <TT
CLASS="TYPE"
>numeric</TT
>) are the responsibility of the
    underlying function implementation and are silently swallowed
    (i.e., not recognized or
    enforced) by the <TT
CLASS="COMMAND"
>CREATE FUNCTION</TT
> command.
   </P
><P
>    <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> allows function
    <I
CLASS="FIRSTTERM"
>overloading</I
>; that is, the same name can be
    used for several different functions so long as they have distinct
    argument types.  However, the C names of all functions must be
    different, so you must give overloaded C functions different C
    names (for example, use the argument types as part of the C
    names).
   </P
><P
>    Two functions are considered the same if they have the same names and
    <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>input</I
></SPAN
> argument types, ignoring any <TT
CLASS="LITERAL"
>OUT</TT
>
    parameters.  Thus for example these declarations conflict:
</P><PRE
CLASS="PROGRAMLISTING"
>CREATE FUNCTION foo(int) ...
CREATE FUNCTION foo(int, out text) ...</PRE
><P>
   </P
><P
>    When repeated <TT
CLASS="COMMAND"
>CREATE FUNCTION</TT
> calls refer to
    the same object file, the file is only loaded once per session.
    To unload and
    reload the file (perhaps during development), start a new session.
   </P
><P
>    Use <A
HREF="sql-dropfunction.html"
><I
>DROP FUNCTION</I
></A
> to remove user-defined
    functions.
   </P
><P
>    It is often helpful to use dollar quoting (see <A
HREF="sql-syntax-lexical.html#SQL-SYNTAX-DOLLAR-QUOTING"
>Section 4.1.2.2</A
>) to write the function definition
    string, rather than the normal single quote syntax.  Without dollar
    quoting, any single quotes or backslashes in the function definition must
    be escaped by doubling them.
   </P
><P
>    To be able to define a function, the user must have the
    <TT
CLASS="LITERAL"
>USAGE</TT
> privilege on the language.
   </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="SQL-CREATEFUNCTION-EXAMPLES"
></A
><H2
>Examples</H2
><P
>   Here are some trivial examples to help you get started.  For more
   information and examples, see <A
HREF="xfunc.html"
>Section 33.3</A
>.
</P><PRE
CLASS="PROGRAMLISTING"
>CREATE FUNCTION add(integer, integer) RETURNS integer
    AS 'select $1 + $2;'
    LANGUAGE SQL
    IMMUTABLE
    RETURNS NULL ON NULL INPUT;</PRE
><P>
  </P
><P
>   Increment an integer, making use of an argument name, in
   <SPAN
CLASS="APPLICATION"
>PL/pgSQL</SPAN
>:
</P><PRE
CLASS="PROGRAMLISTING"
>CREATE OR REPLACE FUNCTION increment(i integer) RETURNS integer AS $$
        BEGIN
                RETURN i + 1;
        END;
$$ LANGUAGE plpgsql;</PRE
><P>
  </P
><P
>   Return a record containing multiple output parameters:
</P><PRE
CLASS="PROGRAMLISTING"
>CREATE FUNCTION dup(in int, out f1 int, out f2 text)
    AS $$ SELECT $1, CAST($1 AS text) || ' is text' $$
    LANGUAGE SQL;

SELECT * FROM dup(42);</PRE
><P>
   You can do the same thing more verbosely with an explicitly named
   composite type:
</P><PRE
CLASS="PROGRAMLISTING"
>CREATE TYPE dup_result AS (f1 int, f2 text);

CREATE FUNCTION dup(int) RETURNS dup_result
    AS $$ SELECT $1, CAST($1 AS text) || ' is text' $$
    LANGUAGE SQL;

SELECT * FROM dup(42);</PRE
><P>
  </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="SQL-CREATEFUNCTION-SECURITY"
></A
><H2
>Writing <TT
CLASS="LITERAL"
>SECURITY DEFINER</TT
> Functions Safely</H2
><P
>    Because a <TT
CLASS="LITERAL"
>SECURITY DEFINER</TT
> function is executed
    with the privileges of the user that created it, care is needed to
    ensure that the function cannot be misused.  For security,
    <A
HREF="runtime-config-client.html#GUC-SEARCH-PATH"
>search_path</A
> should be set to exclude any schemas
    writable by untrusted users.  This prevents
    malicious users from creating objects that mask objects used by the
    function.  Particularly important in this regard is the
    temporary-table schema, which is searched first by default, and
    is normally writable by anyone.  A secure arrangement can be had
    by forcing the temporary schema to be searched last.  To do this,
    write <TT
CLASS="LITERAL"
>pg_temp</TT
> as the last entry in <TT
CLASS="VARNAME"
>search_path</TT
>.
    This function illustrates safe usage:
   </P
><PRE
CLASS="PROGRAMLISTING"
>CREATE FUNCTION check_password(uname TEXT, pass TEXT)
RETURNS BOOLEAN AS $$
DECLARE passed BOOLEAN;
        old_path TEXT;
BEGIN
        -- Save old search_path; notice we must qualify current_setting
        -- to ensure we invoke the right function
        old_path := pg_catalog.current_setting('search_path');

        -- Set a secure search_path: trusted schemas, then 'pg_temp'.
        -- We set is_local = true so that the old value will be restored
        -- in event of an error before we reach the function end.
        PERFORM pg_catalog.set_config('search_path', 'admin, pg_temp', true);

        -- Do whatever secure work we came for.
        SELECT  (pwd = $2) INTO passed
        FROM    pwds
        WHERE   username = $1;

        -- Restore caller's search_path
        PERFORM pg_catalog.set_config('search_path', old_path, true);

        RETURN passed;
END;
$$ LANGUAGE plpgsql SECURITY DEFINER;</PRE
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="SQL-CREATEFUNCTION-COMPAT"
></A
><H2
>Compatibility</H2
><P
>   A <TT
CLASS="COMMAND"
>CREATE FUNCTION</TT
> command is defined in SQL:1999 and later.
   The <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> version is similar but
   not fully compatible.  The attributes are not portable, neither are the
   different available languages.
  </P
><P
>   For compatibility with some other database systems,
   <TT
CLASS="REPLACEABLE"
><I
>argmode</I
></TT
> can be written
   either before or after <TT
CLASS="REPLACEABLE"
><I
>argname</I
></TT
>.
   But only the first way is standard-compliant.
  </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN47392"
></A
><H2
>See Also</H2
><A
HREF="sql-alterfunction.html"
><I
>ALTER FUNCTION</I
></A
>, <A
HREF="sql-dropfunction.html"
><I
>DROP FUNCTION</I
></A
>, <A
HREF="sql-grant.html"
><I
>GRANT</I
></A
>, <A
HREF="sql-load.html"
><I
>LOAD</I
></A
>, <A
HREF="sql-revoke.html"
><I
>REVOKE</I
></A
>, <A
HREF="app-createlang.html"
><I
><I
>createlang</I
></I
></A
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-createdomain.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="sql-creategroup.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>CREATE DOMAIN</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="sql-commands.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>CREATE GROUP</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>