Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <4136BA2E.7080303@jansdal.dk>
Date: Thu, 02 Sep 2004 08:14:06 +0200
From: Steen Jansdal <steen@jansdal.dk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7.1) Gecko/20040707
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Derby, DB2, & Syntax
References: <20040827204519.79260.qmail@web41108.mail.yahoo.com>
 <41360B8E.1040609@Mutagen.Net>
In-Reply-To: <41360B8E.1040609@Mutagen.Net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Jack Klebanoff wrote:
> Jeff Ramsdale wrote:
> 
>>...
>>4) Finally, I believe I saw a reference somewhere
>>indicating beta code existed to allow Derby (or
>>Cloudscape?) to run in-memory only. What's the status
>>of that code and if it's available how would one make
>>use of it?
>>
>>Thanks!
>>
>>Jeff
>>  
>>
> I work for IBM and I am listed on the to-do list 
> <http://incubator.apache.org/derby/DerbyToDo.html> of the Apache/Derby 
> website as being the contact for in-memory database.
> 
> I wrote some code to allow Derby to run in-memory. However, it is not 
> beta code. It is a prototype written to test the 
> org.apache.derby.io.StorageFactory interface and to show that the 
> interface could be used to write an in-memory database.
> 
> The prototype code implements entirely non-persistent dabases. The data 
> goes away when the JVM ends, the code does not automatically save the 
> data to a file at termination nor does it automatically read data from a 
> file when the database starts up. An application can use the normal 
> backup/restore facilities to save and restore to and from a file.
> 
> I have been told that I can contribute the code to the community, though 
> the mechanics of doing so and where it should go remain to be worked 
> out. Is there some interest in the code?
> 
> Jack

Definitely. Let's see the code and if it fits nicely into the
derby code base, I think it would be a win for derby to
include it.

Steen