statement caching proof of concept - Mailing list pgsql-jdbc

From Dave Cramer
Subject statement caching proof of concept
Date
Msg-id 4077BF73-482B-46C8-B65D-2E1FD2465294@fastcrypt.com
Whole thread Raw
Responses Re: statement caching proof of concept  (Heikki Linnakangas <hlinnaka@iki.fi>)
Re: statement caching proof of concept  (till toenges <tt@kyon.de>)
Re: statement caching proof of concept  (Mark Lewis <mark.lewis@mir3.com>)
Re: statement caching proof of concept  (Oliver Jowett <oliver@opencloud.com>)
Re: statement caching proof of concept redux  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc
This is just proof of concept. More work has to be done to make it
build properly and work properly under different jdk's

Couple of questions.

1) What to do if there are multiple concurrent requests per
connection for the same statement?
    1) we could just allow it
    2) we could return a non-cacheable preparedstatement
    3) throw an exception

2) Is it enough to cache prepared statements or should we cache
statements too?

Note: this work is based completely on apache's dbcp statement
caching implementation and this will be noted in the final code.


Attachment

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: Where can I get source for the 7.3 Build
Next
From: "j.random.programmer"
Date:
Subject: Re: Meta Information about columns of a domain datatype ?