RE: [HACKERS] Cache query implemented

On Wed, 1 Mar 2000, Hiroshi Inoue wrote:

> > -----Original Message-----
> > From: Karel Zak - Zakkr [mailto:zakkr@zf.jcu.cz]
> > 
> > On Tue, 29 Feb 2000, Hiroshi Inoue wrote:
> > 
> > > > -----Original Message-----
> > > > From: Karel Zak - Zakkr [mailto:zakkr@zf.jcu.cz]
> > > > 
> > > > > > EXECUTE name [ INTO x, y, ... ] [ USING a, b, ... ]
> > > > > 
> > > > >  This command "Associate input parametrs and output targets 
> > > > with a prepared
> > > > > statement and execute the statement" (SQL92).
> > > > > 
> > > 
> > > I don't know well about PREPARE statement.
> > > But is above syntax for interative SQL command ?
> > > Isn't it for embedded SQL or SQL module ?
> > 
> >  - PREPARE save to cache any standard sql command (OptimizableStmt).
> >  - EXECUTE run this cached plan (query) and send data to frontend or
> >    INTO any relation.
> > 
> >  Or what you mean?
> >
> 
> In old Oracle(I don't know recent Oracle,sorry),PREPARE couldn't be called
> as an interactive SQL command. It was used only in embedded SQL.

 Oh, yes I understand you now. No, prepare is a standard command 
(interactive) (IMO).
 
> Seems x, y  after INTO are output variables. In embedded SQL they are
> host variables. But I don't know what they are in interactive SQL.

 A INTO is same as (example) SELECT ..INTO, see:

 PREPARE myplan AS SELECT * FROM tab;
 EXECUTE myplan INTO newtab;

 A INTO only remove query destination for cached plan.

 ...it is in my implementation. I don't no how it is in any others SQLs.
In my Oracle8's tutorial it isn't. 

						Karel