Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 35609 invoked from network); 24 Sep 2008 15:46:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Sep 2008 15:46:55 -0000 Received: (qmail 38319 invoked by uid 500); 24 Sep 2008 15:46:53 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 38290 invoked by uid 500); 24 Sep 2008 15:46:53 -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 38279 invoked by uid 99); 24 Sep 2008 15:46:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Sep 2008 08:46:52 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rzp2314@gmail.com designates 209.85.200.170 as permitted sender) Received: from [209.85.200.170] (HELO wf-out-1314.google.com) (209.85.200.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Sep 2008 15:45:54 +0000 Received: by wf-out-1314.google.com with SMTP id 26so4681894wfd.13 for ; Wed, 24 Sep 2008 08:46:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=KsF/VJFboQC64moHV1gVuq/NdDpR7usOgBedGh9Rx3A=; b=J5MKiaJtii0SpdENF4AJTjiFk48k+QqkTwEhei8PliXbHInhDIFzu7ujMD+ZNh7uUU 18XaPjkWswLj6r1en1eBSSZ03cEmpxbGED+mGYYwWKfgsDL3mN440IFC5L5vBgIPpEIl MLkvCsFLxCmEdhrkQXOzfEL9mbpjlDPtrZzY8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=HPKm9JwxwWnOWOYICFK1XrtO4QfluFb2vlnxvZdQlrnL8FXX9nf1ukfiK9F1eL1x2h kPgUBMBJw5NaHSRpyai2lBp7BfTrr//KxgQVmlQglEstHJudTK0g0PgE8/wN7HTNiG1u h5NmuGx6e/rkr/E7792DZmWTp7GS4Apqux6m0= Received: by 10.114.161.11 with SMTP id j11mr8274972wae.105.1222271178555; Wed, 24 Sep 2008 08:46:18 -0700 (PDT) Received: by 10.114.203.4 with HTTP; Wed, 24 Sep 2008 08:46:18 -0700 (PDT) Message-ID: Date: Wed, 24 Sep 2008 11:46:18 -0400 From: Zach To: derby-user@db.apache.org, derby-dev@db.apache.org Subject: looking for suggestions- possible extensions to derby MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_88876_4024424.1222271178578" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_88876_4024424.1222271178578 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all, I'm working on a group project for a Database System Implementation class, and we've been tasked with selecting an open source DBMS to add some extensions to. We've decided to go with Apache Derby, but none of us have used it before, so we were hoping to get some input from the general users that have some experience with it. Here are the basic guidelines we have to follow: - Describe three advanced database features you plan to add to this open source software package; the three features must be selected from the following categories: 1. Storage management (including data layout, indexing, buffer management, etc.) 2. Query management (query analysis, compilation, planning, etc.) 3. Transaction management (including recovery from failures) We only have about 6 weeks to work on this project, so we may not have enough time to do anything extremely complicated, but we were hoping you guys would be able to give us suggestions on any shortcomings you have experienced while working with derby, anything you think could be handled better, or something that does not exist that you'd like to see implemented. Our goal is to complete all 3 extensions, but we may not be able to accomplish all of them in the time frame that we have. Thanks in advance for any suggestions you can give us! ~Zach ------=_Part_88876_4024424.1222271178578 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hi all,

I'm working on a group project for a Database System Implementation class, and we've been tasked with selecting an open source DBMS to add some extensions to. We've decided to go with Apache Derby, but none of us have used it before, so we were hoping to get some input from the general users that have some experience with it.

Here are the basic guidelines we have to follow:
-  Describe three advanced database features you plan to add to this open source software package; the three features must be selected from the following categories:
      1. Storage management (including data layout, indexing, buffer management, etc.)
      2. Query management (query analysis, compilation, planning, etc.)
      3. Transaction management (including recovery from failures)

We only have about 6 weeks to work on this project, so we may not have enough time to do anything extremely complicated, but we were hoping you guys would be able to give us suggestions on any shortcomings you have experienced while working with derby, anything you think could be handled better, or something that does not exist that you'd like to see implemented. Our goal is to complete all 3 extensions, but we may not be able to accomplish all of them in the time frame that we have.

Thanks in advance for any suggestions you can give us!

~Zach
------=_Part_88876_4024424.1222271178578--