Subject | Re: [firebird-support] Prepared Statement Caching |
---|---|
Author | Ann W. Harrison |
Post date | 2005-03-03T16:35:01Z |
Scott Buckham wrote:
which has serious on-going maintenance and development. The people who
created Jaybird (and a few others) cleaned up some of the nastier rough
edges of InterClient before Jaybird was released, so our InterClient is
better than the InterBase variant, but still not recommended.
Second, Firebird does cache prepared statement, but only for reuse
within the connection. One of the strengths of most Java systems is
connection pooling, which defeats per-connection anything, including
caches of prepared statements. The term "cognitive dissonance" comes to
mind, as does the introductory wave-theory lab where a waves are
introduced in a lighted water bath in such a way that the water ends up
in regular, pyramid-shaped lumps.
Cheers,
Ann
>First, Jaybird is no longer new - it's a tested and reliable system
> "PreparedStatement caching is impossible! Firebird InterClient 2.01 is
> strongly recommended in preference to other versions of Interbase
> Interclient. Its also worth trying the latest pure Java "JayBird" driver
> (http://www.ibphoenix.com)."
>
which has serious on-going maintenance and development. The people who
created Jaybird (and a few others) cleaned up some of the nastier rough
edges of InterClient before Jaybird was released, so our InterClient is
better than the InterBase variant, but still not recommended.
Second, Firebird does cache prepared statement, but only for reuse
within the connection. One of the strengths of most Java systems is
connection pooling, which defeats per-connection anything, including
caches of prepared statements. The term "cognitive dissonance" comes to
mind, as does the introductory wave-theory lab where a waves are
introduced in a lighted water bath in such a way that the water ends up
in regular, pyramid-shaped lumps.
Cheers,
Ann