Precompiled SQL statement at client side ? (JDBC)

Question

Hi,
Will Oracle support precompiled SQL statement for jdbc client ?
Thanks

Answer 1

A pre-compiled SQL statement on the client side makes absolutely no sense. Let's say the statement refers to system object id 1234 - the EMP table. But in the meantime the EMP table has been dropped and re-created as an index organised table and is now object id 7890.
What about issues like scope, cost-based optimisation, etc?
It honestly does not make the slightest sense to even want such a "pre-compiled client SQL" feature.
> hmm.... Is there anyway to return the compiled SQL
from database ?
Yes - that is exactly what a cursor handle is. You give the database a SQL statement. It parses that and returns a SQL (aka cursor) handle for you to use and re-use.
The typical (stateful) client would use the following template:
-- open a database connection (usually returns a connection/session handle)
hConnection = open DBconnection(params)
-- parse/prepare a SQL statement (returns a SQL/cursor handle)
hSQL = parseSQL( hConnection, 'INSERT INTO foo VALUES( :0, :1 )' )
-- reuse the SQL statement
while (Some_Condition)
loop
Some_Processing()
-- bind values to the SQL statement variables
SQLBind( hSQL, '0', var1)
SQLBind( hSQL, '1', var2)
-- execute the statement (it is not compiled or parsed again by the database)
ExecSQL( hSQL )
endloop