Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 58855 invoked from network); 6 Feb 2003 05:47:06 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 6 Feb 2003 05:47:05 -0000 Received: (qmail 12934 invoked by uid 97); 6 Feb 2003 05:48:43 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@nagoya.betaversion.org Received: (qmail 12927 invoked from network); 6 Feb 2003 05:48:43 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 6 Feb 2003 05:48:43 -0000 Received: (qmail 58492 invoked by uid 500); 6 Feb 2003 05:47:02 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 58478 invoked from network); 6 Feb 2003 05:47:01 -0000 Received: from 12-233-211-9.client.attbi.com (HELO home.nest.cx) (12.233.211.9) by daedalus.apache.org with SMTP; 6 Feb 2003 05:47:01 -0000 Received: (qmail 17991 invoked by uid 1001); 6 Feb 2003 05:47:34 -0000 Sender: greg@home.nest.cx To: "Avalon Developers List" Subject: excalibur datasource: PreparedStatement caching References: X-Key-fingerprint: 2DD1 7CD1 D3C9 FC81 FA66 69B4 7629 A1AE BDA1 1D2E X-Key-available: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8DF5A1B From: Greg Steuck Date: 05 Feb 2003 21:47:34 -0800 In-Reply-To: Message-ID: <86vfzyq7t5.fsf@home.nest.cx> Lines: 15 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Military Intelligence) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >>>>> "Peter" == Peter Royal writes: Peter> Thats fine. My only suggestion would be to also implement a Peter> prepared statement cache so if the same prepared statement Peter> was asked for again, just return the existing instance :) I feel this feature is on a different level. We will need to have a map of released (closed) PreparedStatements associated with each connection. The PreparedStatements will be wrapped into a decorator that intercepts close() and returns the statements into the map (closing any pending ResultSets first). I don't think that a PreparedStatement can be reused until the original caller disposes of it. IMHO, the benefit of such cache is not obvious and I would much rather defer this kind of caching to the database vendor JDBC implementation. --------------------------------------------------------------------- To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: avalon-dev-help@jakarta.apache.org