On Mon, 19 Jun 2006, Dave Cramer wrote:
> This is just proof of concept. More work has to be done to make it build
> properly and work properly under different jdk's
That's neat, but isn't statement caching something that belongs to
the application server, not the JDBC driver?
Also, it seems to me that the changes to AbstractJdbc2Connection and
AbstractJdbc2Statement are completely unrelated to statement caching.
> Note: this work is based completely on apache's dbcp statement caching
> implementation and this will be noted in the final code.
What kind of licensing issues does that bring us?
- Heikki
