commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <bay...@generationjava.com>
Subject Re: [dbutils] StringUtils proposed methods
Date Mon, 11 Nov 2002 17:55:58 GMT


On Mon, 11 Nov 2002, Joe Germuska wrote:

> At 12:23 PM -0500 2002/11/11, Henri Yandell wrote:
> >Looking at these, it seems that the first and third are easier done by
> >using a PreparedStatement, which knows more about exactly how the
> >particular database likes to escape a ' etc.
> >
> >Is there a big need to provide a String method here, or should people just
> >be upgrading to the PreparedStatement?
>
> I have two reasons for building SQL statements from strings instead
> of using prepared statements:
>
> * if you're not iterating through repeated queries, the overhead of
> creating a prepared statement is wasted -- this isn't a critical
> optimization, but it is one argument against using prepared
> statements for one-off queries.  (See
> http://www.onjava.com/pub/a/onjava/2001/12/19/oraclejdbc.html, tip #3)
>
> * When developing, it can be substantially easier to debug JDBC
> problems when you can see the values which were used in the SQL
> statement; this is easier done by printing a complete SQL statement
> than by reconstructing it.

[P6Spy!  though it's not quite there yet with the log rolling stuff]

> I think these are pretty good reasons for leaving the choice up to
> users of the library, instead of steering people straight to
> PreparedStatements in all cases...

Yeah. Am convinced that they would be of use in DbUtil class, or a
DbStringUtil.class.

Want to send your implementation in Ken? As I'm inherently lazy

Hen


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message