Re: Precompiled statement?

joeNOSPAM@[EMAIL PROTECTED]
 wrote:
> The driver sends the SQL string to the DBMS. The DBMS parses it, and
> compiles/creates a plan for executing what the SQL wants. This
> includes
> verifying the names of tables and columns etc, choosing what index to
> use etc. This plan may include place-holders for data values passed in
> as parameters. This is very similar to a session-scoped stored
> procedure.
>   Then, when the driver sends the needed parameter values, and says
> 'go',
> the DBMS executes the plan.

That is what a good database and a good JDBC driver does.

And what the name PreparedStatement clearly indicates is the
intention.

But there are AFAIK no guarantee that this is actually happening.

So one should check what the specific database does before
claiming that prepared statement improves performance.

No need to check before choosing prepared statement, because
there are so many other advantages of using it.

Some years ago I tested Oracle and MySQL. Oracle obviously did
the right thing and prepared statement improved performance
significantly. On MySQL prepared statement reduced performance
(MySQL first introduced PREPARE in version 5.0).

Arne