| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: statement caching proof of concept |
| Date: | 2006-06-19 18:33:53 |
| Message-ID: | AA9D09A0-B23D-442E-9DB5-AE5364BE588A@fastcrypt.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 19-Jun-06, at 2:07 PM, Heikki Linnakangas wrote:
> 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?
There's an interesting question. However the way it has been done it
can be very easily removed, or added.
>
> 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?
None, their license is more or less bsd.
>
> - Heikki
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | till toenges | 2006-06-19 18:57:26 | Re: statement caching proof of concept |
| Previous Message | Kris Jurka | 2006-06-19 18:22:09 | Re: moving to java 1.6 |