[ 
https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676902#action_12676902
 ] 

Cheng Che Chen commented on DERBY-646:
--------------------------------------

I have just emailed scanned images of signed ICLA to [email protected], as 
instructed by Kathey Marsden.

Regarding Rick Hillegas' question about the tests included in my patch, there 
are three sets of unit tests and one functional test.

The unit tests verify the correctness of my internal data structures.  They are 
probably not useful to other implementations, unless, for example, they have 
similar properties to be verified.

The functional test implements an application in both JAVA and SQL and 
cross-checks the computed results.  It can indeed be applied to any 
implementation of storage factory by simply changing the database name for the 
SQL portion of the test object.  The functional test consists of the following 
files: "GenMog.java", "SampMog.java", "ClusMog.java", "ClusMogSQL.java", and 
"MogTest.java" -- the last file is the JUnit test object.

However, I have some doubt about whether I have configured/used Derby's test 
framework properly in "MogTest.java".  This file started out as a stand-alone 
JUnit test.  When I was running it stand-alone, it would incur no disk 
activity.  After I converted the file to run under Derby's test framework, the 
disk activity LED on my computer would go wild every time I ran it.  I wonder 
if I have unwittingly been testing the default storage factory with the 
converted test.

> In-memory backend storage support
> ---------------------------------
>
>                 Key: DERBY-646
>                 URL: https://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, derby-646-20090222.diff, 
> derby-646-20090222.stat, derby-646-2a-vfmem_first_rev.diff, 
> derby-646-2a-vfmem_first_rev.stat, derby-646-performance_comparison_1a.txt, 
> svn.diff
>
>
> To allow creation and modification of databases in-memory without requiring 
> disk access or space to store the database.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to