Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 11976 invoked from network); 23 Jul 2004 13:43:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 23 Jul 2004 13:43:12 -0000 Received: (qmail 77643 invoked by uid 500); 23 Jul 2004 13:43:11 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 77532 invoked by uid 500); 23 Jul 2004 13:43:10 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 77518 invoked by uid 99); 23 Jul 2004 13:43:10 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.137.167.162] (HELO filter.fridayfives.net) (209.137.167.162) by apache.org (qpsmtpd/0.27.1) with ESMTP; Fri, 23 Jul 2004 06:43:07 -0700 Received: by filter.fridayfives.net (Postfix, from userid 5054) id EDC936FC90; Fri, 23 Jul 2004 08:33:21 -0400 (EDT) Received: from freki (freki [127.0.0.1]) by freki (Postfix) with SMTP id ADB5B6FCAA for ; Fri, 23 Jul 2004 08:33:20 -0400 (EDT) Received: from [192.168.1.30] (kite.forthill.int [192.168.1.30]) by filter.fridayfives.net (Postfix) with ESMTP id 8F0936FC90 for ; Fri, 23 Jul 2004 08:33:20 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Message-Id: <35F23132-DCAE-11D8-9B70-000A95782782@forthillcompany.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: OJB Developers List From: Brian McCallister Subject: [RT] Cache Aware JDBC Driver/DataSource Date: Fri, 23 Jul 2004 09:42:59 -0400 X-Mailer: Apple Mail (2.618) X-Spam-Bayes-Score: 0.0000 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on freki X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I haven't explored the various existing JDBC proxy drivers enough to know which would be easiest to use, or if implementing one would be, but a potential way of solving a number of dirty-cache issues might be to somewhere provide a JDBC Driver/DataSource which understands OJB metadata and can interact with the OJB cache in order to dirty things it sees pass through. Anything talking raw JDBC can then use this driver, which delegates to the real driver, and is cache aware so can dirty the cache =) -Brian --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org