From: | Mike Mascari <mascarm(at)mascari(dot)com> |
---|---|
To: | Rod Taylor <rbt(at)zort(dot)ca> |
Cc: | 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 16:55:23 |
Message-ID: | 3D3D8A7B.5D371854@mascari.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Rod Taylor wrote:
>
> On Tue, 2002-07-23 at 11:34, Tom Lane wrote:
> > nconway(at)klamath(dot)dyndns(dot)org (Neil Conway) writes:
> > > Regarding the syntax for EXECUTE, it occurs to me that it could be made
> > > to be more similar to the PREPARE syntax -- i.e.
> >
> > > PREPARE foo(text, int) AS ...;
> >
> > > EXECUTE foo('a', 1);
> >
> > > (rather than EXECUTE USING -- the effect being that prepared statements
> > > now look more like function calls on a syntactical level, which I think
> > > is okay.)
> >
> > Hmm, maybe *too* much like a function call. Is there any risk of a
> > conflict with syntax that we might want to use to invoke stored
> > procedures? If not, this is fine with me.
>
> Stored procedures would use PERFORM would they not?
>
> I like the function syntax. It looks and acts like a temporary 'sql'
> function.
FWIW, Oracle uses EXECUTE to execute stored procedures. It is not apart
of the SQL language, but a SQL*Plus command:
EXECUTE my_procedure();
The Oracle call interface defines a function to call stored procedures:
OCIStmtExecute();
Likewise, the privilege necessary to execute a stored procedure is
'EXECUTE' as in:
GRANT EXECUTE ON my_procedure TO mascarm;
Again, FWIW.
Mike Mascari
mascarm(at)mascari(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2002-07-23 19:56:39 | Re: [PATCHES] Demo patch for DROP COLUMN |
Previous Message | Neil Conway | 2002-07-23 16:46:15 | Re: [PATCHES] prepareable statements |
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Tkach | 2002-07-23 16:55:33 | JDBC timestamp does not understand [-]infinity |
Previous Message | Neil Conway | 2002-07-23 16:46:15 | Re: [PATCHES] prepareable statements |