Hi,
I think what Thomas means to say is that:
PreparedStatement is equivalent to invoking a Java API for a
pre-optimized query
If you invoke a Java API as you're asking for, you should get
performance equal to:
PreparedStatement + Overhead to optimize the query
So... measure the overhead of invoking the same query using
Statement vs PreparedStatement and that's the best-case scenario you
will ever get (it assumes the cost of optimizing the query is zero). If
the value you get is really small it means removing SQL isn't really
worth it.
Gili
On 17/02/2012 1:42 PM, java dev wrote:
Does H2 provide the option to try it out? Can you point to a
documentation if available?
On Feb 17, 1:01 pm, Thomas Mueller<[email protected]>
wrote:
Hi,
what kind of overhead is associated with SQL parsing?
Not much (you can try yourself). But for best results, use a PreparedStatement.
Regards,
Thomas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
