I agree about the coupling between the JDBC and JCA classes - it was a
bit of a mess to try to figure out how to get the classes to work
together and I had to make too many functions public that should have
been package. I wasn't sure of the best place to start but wanted to
get something done quick to speed up certain parts of my application.
You can keep the patch or throw it away, but I have to share my
modifications for LGPL!

Let me take look at the src\pool directory and see what is in that
folder. Is it fully implemented or does it need work?

-----Original Message-----
From: Roman Rokytskyy [mailto:rrokytskyy@...]
Sent: Thursday, May 29, 2003 4:58 PM
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] Re: Patch: pooled prepared statements

Ken,

> I have heard that pooled prepared statements are part of JDBC3.0 but
> have not looked at the spec. Here is a patch that will implement
> prepared statement pooling. The patch is against the 1.0 version of
> the driver.

Thank you for the patch. However currently I'm thinking about
implementing statement pooling on the API level (JDBC level connection
and statement pooling is already in the CVS in client-java/src/pool/
directory). Implementing it on the API level adds generic mechanism of
statement handle pooling. The only problem I see is to decrease
coupling between instances of java.sql.Statement class (and
subclasses) and API objects.

Will you be interested in working in that direction?

Thanks!
Roman Rokytskyy



To unsubscribe from this group, send an email to:
Firebird-Java-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/