Re: [MO-java-dev] CommonMockConnection and Statement

[Olaf K. <ok...@ab...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


| Don't think there's any reason, just no one has needed to do that yet.

My comment has nothing to do with MockConnection, but usually it is
better for database performance if you use prepared statements, at least
if there are variable parameters.

(At least some) databases cache statements execution plans and use the
string statement as key for the plan - this doesn't work with changing
parameters in every execute. Even worse, as the database cache is
limited in size, it may be that ad hoc statements even make prepared
statements flush from the cache.

(On the other hand, perfect reasons for adhoc statements exist, just
wanted to share this thought)

Olaf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+e0XC7/xtFKqdCzURAt8vAJ4m3dukx5iz8d+K/LSbw677mepicgCfeVvG
ExnOp/4rx2kvY2Gpf7n9F8c=
=v08c
-----END PGP SIGNATURE-----