Embedded SQL versus stored procedures

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 Wed Oct 04 2000 - 21:36:14 CDT