2002-08-27 06:55:12 +02:00
|
|
|
<!--
|
2003-04-27 01:56:51 +02:00
|
|
|
$Header: /cvsroot/pgsql/doc/src/sgml/ref/execute.sgml,v 1.4 2003/04/26 23:56:51 petere Exp $
|
2002-08-27 06:55:12 +02:00
|
|
|
PostgreSQL documentation
|
|
|
|
-->
|
|
|
|
|
|
|
|
<refentry id="SQL-EXECUTE">
|
|
|
|
<refmeta>
|
|
|
|
<refentrytitle id="sql-execute-title">EXECUTE</refentrytitle>
|
|
|
|
<refmiscinfo>SQL - Language Statements</refmiscinfo>
|
|
|
|
</refmeta>
|
2003-04-27 01:56:51 +02:00
|
|
|
|
2002-08-27 06:55:12 +02:00
|
|
|
<refnamediv>
|
2003-04-27 01:56:51 +02:00
|
|
|
<refname>EXECUTE</refname>
|
|
|
|
<refpurpose>execute a prepared statement</refpurpose>
|
2002-08-27 06:55:12 +02:00
|
|
|
</refnamediv>
|
2003-01-19 01:13:31 +01:00
|
|
|
|
2003-04-27 01:56:51 +02:00
|
|
|
<refsynopsisdiv>
|
|
|
|
<synopsis>
|
|
|
|
EXECUTE <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable class="PARAMETER">parameter</replaceable> [, ...] ) ] [ INTO [ TEMPORARY | TEMP ] <replaceable class="PARAMETER">table</replaceable> ]
|
|
|
|
</synopsis>
|
2002-08-27 06:55:12 +02:00
|
|
|
</refsynopsisdiv>
|
|
|
|
|
2003-04-27 01:56:51 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Description</title>
|
2002-08-27 06:55:12 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
<command>EXECUTE</command> is used to execute a previously prepared
|
2003-04-27 01:56:51 +02:00
|
|
|
statement. Since prepared statements only exist for the duration of a
|
|
|
|
session, the prepared statement must have been created by a
|
2002-08-27 06:55:12 +02:00
|
|
|
<command>PREPARE</command> statement executed earlier in the
|
|
|
|
current session.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2003-04-27 01:56:51 +02:00
|
|
|
If the <command>PREPARE</command> statement that created the statement
|
2002-08-27 06:55:12 +02:00
|
|
|
specified some parameters, a compatible set of parameters must be
|
|
|
|
passed to the <command>EXECUTE</command> statement, or else an
|
2003-04-27 01:56:51 +02:00
|
|
|
error is raised. Note that (unlike functions) prepared statements are
|
|
|
|
not overloaded based on the type or number of their parameters; the
|
|
|
|
name of a prepared statement must be unique within a database session.
|
2002-08-27 06:55:12 +02:00
|
|
|
</para>
|
|
|
|
|
2003-01-19 01:13:31 +01:00
|
|
|
<para>
|
|
|
|
Like <command>SELECT INTO</command>, <command>EXECUTE</command> can
|
2003-04-27 01:56:51 +02:00
|
|
|
store the results of executing a query into a newly-created
|
|
|
|
table, by specifying an <literal>INTO</> clause. For more information on this behavior,
|
2003-02-03 00:46:38 +01:00
|
|
|
see <xref linkend="sql-selectinto" endterm="sql-selectinto-title">.
|
2003-01-19 01:13:31 +01:00
|
|
|
</para>
|
|
|
|
|
2002-08-27 06:55:12 +02:00
|
|
|
<para>
|
2003-04-27 01:56:51 +02:00
|
|
|
For more information on the creation and usage of prepared statements,
|
2002-08-27 06:55:12 +02:00
|
|
|
see <xref linkend="sql-prepare" endterm="sql-prepare-title">.
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
2003-04-27 01:56:51 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Parameters</title>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable class="PARAMETER">plan_name</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The name of the prepared statement to execute.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2002-08-27 06:55:12 +02:00
|
|
|
|
2003-04-27 01:56:51 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable class="PARAMETER">parameter</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The actual value of a parameter to the prepared statement. This
|
|
|
|
must be an expression yielding a value of a type compatible with
|
|
|
|
the data type specified for this parameter position in the
|
|
|
|
<command>PREPARE</command> command that created the prepared
|
|
|
|
statement.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable class="PARAMETER">table</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The name of the table in which to store the results of executing
|
|
|
|
the statement (if it is a <command>SELECT</command>). If no
|
|
|
|
table is specified, the results are returned to the client (as
|
|
|
|
normal).
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Compatibility</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The SQL standard includes an <command>EXECUTE</command> statement,
|
|
|
|
but it is only for use in embedded SQL. This version of the
|
|
|
|
<command>EXECUTE</command> statement also uses a somewhat different
|
|
|
|
syntax.
|
|
|
|
</para>
|
2002-08-27 06:55:12 +02:00
|
|
|
</refsect1>
|
|
|
|
</refentry>
|
|
|
|
|
|
|
|
<!-- Keep this comment at the end of the file
|
|
|
|
Local variables:
|
|
|
|
mode: sgml
|
|
|
|
sgml-omittag:nil
|
|
|
|
sgml-shorttag:t
|
|
|
|
sgml-minimize-attributes:nil
|
|
|
|
sgml-always-quote-attributes:t
|
|
|
|
sgml-indent-step:1
|
|
|
|
sgml-indent-data:t
|
|
|
|
sgml-parent-document:nil
|
|
|
|
sgml-default-dtd-file:"../reference.ced"
|
|
|
|
sgml-exposed-tags:nil
|
|
|
|
sgml-local-catalogs:"/usr/lib/sgml/catalog"
|
|
|
|
sgml-local-ecat-files:nil
|
|
|
|
End:
|
|
|
|
-->
|