db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cheng Che Chen (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-646) In-memory backend storage support
Date Tue, 17 Feb 2009 06:39:59 GMT

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

chatom edited comment on DERBY-646 at 2/16/09 10:38 PM:
----------------------------------------------------------------

Thanks for the tip on the "extraDBMSclasses.properties" file.  I'm now able to build the JAR
files properly with my classes.

At this point, I have JUnit test cases for the basic building blocks of my implementation.
 They run successfully stand-alone, but I have yet to figure out how to integrate them into
Derby's test framework.

I have also done some manual functional testing of my in-memory storage factory using examples
from the Derby tutorial (http://db.apache.org/derby/papers/DerbyTut/index.html).

I have not modified any existing Derby tests to use the new in-memory storage factory, as
I have yet to figure out how Derby's test framework works.

All source files for this implementation are contained in a new sub-directory "java/engine/org/apache/derby/impl/io/memory".
 There is no change to any public API nor to any existing JAVA source file.  One line was
added to "java/engine/org/apache/derby/impl/build.xml", and one line was added to "tools/jar/extraDBMSclasses.properties",
for the new source files to build.

If people are willing to have a look at what I have so far, then I will post the patch; otherwise,
please wait until I have plugged things into the Derby test framework.


      was (Author: chatom):
    Thanks for the tip on the "extraDBMSclasses.properties" file.  I'm now able to build the
JAR files properly with my classes.

At this point, I have JUnit test cases for the basic building blocks of my implementation.
 They run successfully stand-alone, but I have yet to figure out how to integrate them into
Derby's test framework.

I have also done some manual functional testing of my in-memory storage factory using examples
from the Derby tutorial (http://db.apache.org/derby/papers/DerbyTut/index.html).

I have not modified any existing Derby tests to use the new in-memory storage factory, as
I have yet to figure out how Derby's test framework works.

If people are willing to have a look at what I have so far, then I will post the patch; otherwise,
please wait until I have plugged things into the Derby test framework.

  
> 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,
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.


Mime
View raw message