--- jon gold <[EMAIL PROTECTED]> wrote:
> i notice that QueryRunner.query always prepares a statement -- even if
> there are no replacement parameters. why is this?
You don't need replacement parameters to benefit from caching and reusing
PreparedStatement instances.
>
> the reason i ask is t
i notice that QueryRunner.query always prepares a statement -- even if
there are no replacement parameters. why is this?
the reason i ask is that it leads to undue bloat on a statement pool
when used in conjunction with a connection from a connection pool. in
our case, we eventually get OutOfMe
