Re: [PATCHES] prepareable statements

From: Joe Conway <mail(at)joeconway(dot)com>
To: Mike Mascari <mascarm(at)mascari(dot)com>
Cc: Rod Taylor <rbt(at)zort(dot)ca>, Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] prepareable statements
Date: 2002-07-23 23:23:30
Message-ID: 3D3DE572.3050602@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Mike Mascari wrote:
> FWIW, Oracle uses EXECUTE to execute stored procedures. It is not apart
> of the SQL language, but a SQL*Plus command:
>
> EXECUTE my_procedure();
>

Also with Transact SQL (i.e. MSSQL and Sybase)

Syntax
Execute a stored procedure:
[[EXEC[UTE]]
{
[(at)return_status =]
{procedure_name [;number] | @procedure_name_var
}
[[(at)parameter =] {value | @variable [OUTPUT] | [DEFAULT]]
[,...n]
[WITH RECOMPILE]

However, as Peter E. has pointed out, SQL99 uses the keyword CALL:

15.1 <call statement>
Function
Invoke an SQL-invoked routine.
Format
<call statement> ::= CALL <routine invocation>

FWIW,

Joe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2002-07-23 23:28:45 Re: Access Two Databases
Previous Message Bruce Momjian 2002-07-23 23:16:29 Re: C vs. C++ contributions

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2002-07-23 23:59:15 Re: lock listing
Previous Message Bruce Momjian 2002-07-23 23:13:52 Re: Fk fix for noaction update/delete