Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 30943 invoked from network); 24 Jan 2008 22:59:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Jan 2008 22:59:12 -0000 Received: (qmail 62653 invoked by uid 500); 24 Jan 2008 22:58:57 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 62622 invoked by uid 500); 24 Jan 2008 22:58:57 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 62596 invoked by uid 99); 24 Jan 2008 22:58:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2008 14:58:57 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2008 22:58:51 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id F2C9A71426E for ; Thu, 24 Jan 2008 14:58:43 -0800 (PST) Message-ID: <26012008.1201215523987.JavaMail.jira@brutus> Date: Thu, 24 Jan 2008 14:58:43 -0800 (PST) From: "Dibyendu Majumdar (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-3351) Implement a Pluggable Storage Engine Architecture in Derby MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Implement a Pluggable Storage Engine Architecture in Derby ---------------------------------------------------------- Key: DERBY-3351 URL: https://issues.apache.org/jira/browse/DERBY-3351 Project: Derby Issue Type: New Feature Components: Services, SQL, Store Reporter: Dibyendu Majumdar Assignee: Dibyendu Majumdar My aim is to create a pluggable storage engine architecture for Derby, so that the default store implementation can be replaced with alternative storage engines. I have created my own storage engine which I would like to use with Derby's SQL layer, so that is a motivation. But I also think that this will benefit the community, and could be the lead to a pluggble storage engine architecture similar to that of MySQL. I am not yet sure where the storage engine boundary should lie. I would welcome input in this area. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.