Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Date: Tue, 14 Nov 2006 22:12:02 +0100
From: Kristian Waagan <Kristian.Waagan@Sun.COM>
Subject: Re: [jira] Updated: (DERBY-646) In-memory backend storage support
In-reply-to: <4559F943.8050104@vancouvering.com>
Sender: Kristian.Waagan@Sun.COM
To: derby-dev@db.apache.org
Message-id: <455A3122.5010408@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT
References: <10832575.1163509722076.JavaMail.jira@brutus>
 <4559F943.8050104@vancouvering.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20061024)

David Van Couvering wrote:
> Great to see you working on this, Kristian.  Regarding the CLA, we went 
> through this a while ago, and yes, it is sufficient.

Thanks for the clarification.

Just want to point out that I am not actively working on this issue, so 
anyone else that want to pick it up is welcome to do so :)
I just felt it had been abandoned for too long, and wanted to give it a 
little "kick behind" since there seems to be interest for the feature in 
the (user) community.


-- 
Kristian

> 
> David
> 
> Kristian Waagan (JIRA) wrote:
>>      [ http://issues.apache.org/jira/browse/DERBY-646?page=all ]
>>
>> Kristian Waagan updated DERBY-646:
>> ----------------------------------
>>
>>     Attachment: derby-646-1a-raw-compiles.diff
>>                 derby-646-1a-raw-compiles.stat
>>
>> 'derby-646-1a-raw-compiles.diff' is a minor fix of the original patch 
>> 'svn.diff'. The patch now applies to trunk and compiles. No other 
>> clean-ups/changes have been done, but I had to rewrite a little bit to 
>> solve circular compile dependencies.
>>
>> As far as I can tell, the basic functionality is working. I was able 
>> to run with the memory storage backend, which creates a database 
>> directory with lock files and a tmp directory. Tried running a few 
>> tests with a "hacked" JDBCClient implementation, and the tests passed. 
>> Had some problems with warnings regarding dual boot (missing 
>> shutdown/clean-up?).
>>
>> I think a little more clean-up should be done first (implement a 
>> missing method - getURL, remove commented out code, add some more 
>> comments), and then the patch can be reviewed for functional/design 
>> improvements.
>> We might want some tests written specifically for the memory backend, 
>> and then run the existing tests with the memory backend as well.
>>
>> Stephen Fitch is listed at 
>> http://people.apache.org/~jim/committers.html under "Unlisted CLAs". 
>> Is this enough to allow us to safely bring this code into the repository?
>>
>>> In-memory backend storage support
>>> ---------------------------------
>>>
>>>                 Key: DERBY-646
>>>                 URL: http://issues.apache.org/jira/browse/DERBY-646
>>>             Project: Derby
>>>          Issue Type: New Feature
>>>          Components: Store
>>>         Environment: All
>>>            Reporter: Stephen Fitch
>>>         Attachments: derby-646-1a-raw-compiles.diff, 
>>> derby-646-1a-raw-compiles.stat, svn.diff
>>>
>>>
>>> To allow creation and modification of databases in-memory without 
>>> requiring disk access or space to store the database.
>>