Re: Embedded SQL versus stored procedures

Yes. Oracle needs no special commands to tell it to cache the execution plan. The subsequent statements must match letter for letter, space for space, case sensitive, except for bind variables.

So select * from emp <> SelEct * from emp bu select * from emp where empid = :1 == select * from emp where empid =:1 and the bind variables are different.

Chris Hopkins wrote:

> What are the good arguments for one versus the other. The environment
> is a multithreaded C++ application in a turn-key Unix system. Not a lot
> of end user involvement. No GUI.
>
> In the old days I used "EXEC SQL REPEATED [insert,update,select...] to
> cause the Ingres DB engine to cache the SQL and resulting execution
> plan. Does such exist within Oracle Embedded SQL? Are the mechanics
> within the Oracle server smart enough to recognize the same EXEC SQL
> block, and therefore automatically make use of a cached execution plan?
>
> Thanks,
Received on Thu Oct 05 2000 - 04:42:49 CEST